Skip to main content
Glama

Publish template

publish_template

Publish a template's draft: the changes saved by update_template, add_objects, update_objects and remove_objects (or made in the web editor) become the published version, which is what the share link, the presentation, teammates and export_pptx(template_id) show. A new entry is added to the version history; the previous published version stays there and can be restored on the web. Requires a Pro account. Input: the template id, an optional one-line note (up to 100 characters) for the history, and optionally expected_draft_version (the draft_version you last saw) so a draft someone else changed since is not published by mistake. Returns version_number (the history number, v1, v2, ...), published_version and the url. Errors: pro_required, not_found, no_draft (there are no unpublished changes), conflict (the draft changed since expected_draft_version; read it again with get_template(draft: true)), invalid_input.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "publish_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTemplate id from list_templates.
noteNoA short note on what changed, one line, up to 100 characters.
expected_draft_versionNoThe draft_version from get_template(draft: true) or your last save. Given, the call fails with conflict if the draft changed since.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that a version history entry is created, that the previous published version is retained and restorable on the web, that a Pro account is required, and that a concurrency guard exists via expected_draft_version. It also enumerates the exact error codes (pro_required, not_found, no_draft, conflict, invalid_input) and the recovery path for conflict, which annotations cannot convey.

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

Conciseness4/5

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

Front-loaded with the core action and its effect, then parameters, then errors. Every clause carries information, though the dense nested parentheticals make it heavier than necessary for a three-parameter tool.

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

Completeness5/5

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

With no output schema, the description still documents the return payload (version_number, published_version, url), covers prerequisites (Pro account) and the full error surface, and explains optimistic-concurrency semantics. An agent has everything needed to call this correctly and to handle failures.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description rises above it by explaining why expected_draft_version exists ('the draft_version you last saw' so someone else's change is not published by mistake) and how to recover on conflict via get_template(draft: true). The note parameter's purpose is restated from the schema with only marginal added meaning.

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?

States a specific verb and resource ('Publish a template's draft') and immediately defines the resulting state change: draft edits become the published version. It is clearly separable from update_template/add_objects/remove_objects, which it names as the producers of the draft, and from export_pptx and the share link, which it names as consumers.

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?

Gives strong contextual guidance: publishing is the step that makes draft changes visible to the share link, presentation, teammates and export, and it names the error case where there are no unpublished changes (no_draft). It does not explicitly state when to prefer save_template or update_template instead, but the draft-vs-published framing makes the boundary inferable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources