Skip to main content
Glama
andyyaro

Tableau Public Authoring MCP

by andyyaro

publish_to_tableau_public

Publish an open workbook to Tableau Public with a required confirmation flag to prevent accidental release. The workbook becomes world-visible and irreversibly public.

Instructions

DESTRUCTIVE / PUBLIC. Publish an open workbook to the user's Tableau Public account through the visible Server > Tableau Public > Save to Tableau Public workflow. Publication is irreversible and world-visible. Requires confirm_publish=true. Never reads credentials; pauses for manual sign-in if required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoReport what would happen without publishing.
profileYesYour Tableau Public profile name. Required to resolve and verify the resulting public URL after publication.
overwriteNoAllow overwriting an existing workbook of the same name.
set_titleNoType public_name into the dialog's Workbook Title field. If false, Tableau's pre-filled title (from the file name) is kept.
public_nameYesName for the published workbook (must be unique)
workbook_pathNoAbsolute path to the .twbx being published. Optional but recommended: it lets a minimized workbook be raised reliably with `open -a` instead of a coordinate click.
screenshot_dirNo
confirm_publishYesMust be true. Guards against accidental publication.
workbook_windowYesThe open workbook's exact name (its window title without the 'Tableau Public - ' prefix). Matched exactly, not as a substring, because publishing is irreversible: a substring match would let 'Q3_Sales' publish 'Q3_Sales_Draft'.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It explicitly labels the action as 'DESTRUCTIVE / PUBLIC,' states 'Publication is irreversible and world-visible,' highlights the guard (confirm_publish=true), and discloses manual sign-in behavior. This is comprehensive, though it could mention error handling or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: the first focuses on purpose and danger, the second on key details (irreversibility, guard, credential handling). No waste, front-loaded with the most critical information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive 9-parameter tool with no output schema, the description covers the essential aspects: irreversible publication, required guard, credential handling, and exact window name matching. It could mention return behavior or failure scenarios, but it is sufficiently complete for safe usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 89%, so the schema already documents most parameters. The description adds little beyond what's in the schema (e.g., reiterates confirm_publish must be true and workbook_window exact matching). Baseline 3 is appropriate as it does not need to compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with 'DESTRUCTIVE / PUBLIC. Publish an open workbook to the user's Tableau Public account...' and clearly distinguishes the tool from siblings like validate_workbook_spec or verify_published_workbook. The verb 'Publish' and resource 'open workbook to Tableau Public' are precise.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states 'Requires confirm_publish=true' and 'Never reads credentials; pauses for manual sign-in if required,' providing clear usage context. However, it does not explicitly state when not to use the tool or suggest alternatives among the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andyyaro/tableau-public-authoring-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server