Summary
The Tableau MCP tools currently return content metadata (name, owner, tags,
workbook updatedAt) but not the refresh/schedule/governance data that's
visible in the Tableau UI. Requesting new tools (or extended responses) to
expose the following via the Tableau REST API v3.19.
Requested capabilities
- Extract last refresh time –
extractLastRefreshTime / extractLastUpdateTime
(from GET /sites/{site}/datasources/{id})
- Refresh schedules + suspended state –
GET /sites/{site}/tasks/extractRefreshes
- Refresh job status / failure counts –
GET /sites/{site}/jobs?jobType=RefreshExtract
(to detect failed / suspended-after-N-tries)
- Workbook → datasource mapping –
GET /sites/{site}/workbooks/{id}/connections
(to flag weakest-link stale extracts, e.g. 4/5 fresh, 1 stale)
- PII / sensitivity labels – data quality warnings / labels API
Use case
Build a per-dashboard health report showing last refresh time, schedule,
failed refreshes, stale extracts, and PII flags — currently blocked because
these fields aren't wrapped by the MCP.
Notes
Summary
The Tableau MCP tools currently return content metadata (name, owner, tags,
workbook
updatedAt) but not the refresh/schedule/governance data that'svisible in the Tableau UI. Requesting new tools (or extended responses) to
expose the following via the Tableau REST API v3.19.
Requested capabilities
extractLastRefreshTime/extractLastUpdateTime(from
GET /sites/{site}/datasources/{id})GET /sites/{site}/tasks/extractRefreshesGET /sites/{site}/jobs?jobType=RefreshExtract(to detect failed / suspended-after-N-tries)
GET /sites/{site}/workbooks/{id}/connections(to flag weakest-link stale extracts, e.g. 4/5 fresh, 1 stale)
Use case
Build a per-dashboard health report showing last refresh time, schedule,
failed refreshes, stale extracts, and PII flags — currently blocked because
these fields aren't wrapped by the MCP.
Notes
role. Some of the above (jobs/schedules) may require elevated permissions —
flagging so it can be scoped.