Skip to main content

Tableau MCP and evidence mapping

Capability discovery​

Tableau MCP implementations differ. Inspect the live tool catalog and each relevant schema. Select read tools by described behavior, not guessed names. Record server identity when exposed, content types and stable identifiers, filters and page controls, field semantics, visibility limits, errors, and incomplete pages.

Use read operations for evidence collection. Use writes only in the entrypoint’s explicitly authorized remediation phase. If the catalog does not establish an operation’s effect, stop before calling it.

Canonical internal fields​

Normalize only observed properties:

Internal fieldMeaning
idStable Tableau identifier as returned
typeproject, workbook, view, datasource, or other returned type
nameDisplay name
project_idStable containing-project identifier
owner_idStable owner identifier
created_atDocumented creation/publish timestamp
modified_atDocumented content modification timestamp
usageMetric value plus metric name and exact time semantics
certificationExplicit returned certification status
descriptionReturned description; preserve absent versus empty
tagsReturned tags; preserve absent versus empty
lineageExplicit upstream/downstream IDs and relation type

Keep the raw source property name beside normalized fields when ambiguity is possible.

Product-semantics guardrails​

Current Tableau REST documentation exposes view/workbook modification timestamps and can optionally return a view's totalViewCount. The latter is a total count, not a recent time window. Tableau REST list methods can paginate, but limits differ by method; follow the live MCP schema and response rather than imposing one global page size.

Tableau Metadata API can support discovery and lineage analysis when exposed by the connected MCP server and permitted for the identity. Its existence in Tableau does not prove that a particular MCP server provides it.

Official references:

Degradation​

FailureResponse
Core inventory unavailableStop; state connection/access blocker
One content type unavailableContinue only if useful; mark its domains not assessed
One page or batch failsRetry only if safe and likely transient; otherwise preserve partial coverage
Rate limitHonor server guidance; avoid fixed sleep claims
Missing propertyDo not synthesize it; mark the affected rule not assessed
Unresolved joinKeep both records and report the join gap

Do not repeatedly retry authorization failures. Do not translate API visibility into a claim about total site inventory.