Skip to main content
Glama

Publish a scheduled publication or draft now

publish_publication

Publish a scheduled publication or a draft immediately instead of at its time. This posts publicly unless a platform's privacy setting says otherwise, so confirm with the user first. Poll get_publication for progress.

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": {
      "publicationId": "<publicationId>"
    },
    "name": "publish_publication"
  }
}

Input Schema

NameRequiredDescriptionDefault
publicationIdYesA publication id from create_publication or list_publications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses a real side effect — the post becomes publicly visible unless a platform privacy setting overrides it — and that the operation is asynchronous. It does not address failure modes, whether publishing is reversible, or what happens if the publication is already live.

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?

Three short sentences, each doing distinct work: what it does, the visibility risk plus confirmation cue, and the polling follow-up. Front-loaded with no filler or repetition of the title.

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 one-parameter mutation tool with no output schema and no contradictions with its annotations, the definition covers the essential risks (public visibility, confirmation) and the async workflow. Only error/edge-case behavior is left unstated, which is a minor gap.

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 coverage is 100% and the single parameter's description already explains where a publicationId comes from (create_publication or list_publications). The prose adds no further meaning about the parameter, so the baseline 3 applies.

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

Purpose4/5

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

The description gives a specific verb and resource ('Publish a scheduled publication or a draft') and clarifies the key semantic distinction — publishing now rather than at the scheduled time. It is clearly different from get_publication/cancel_publication/update_publication, though it does not explicitly name those siblings as alternatives.

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?

It states an actionable precondition ('confirm with the user first') and a follow-up path ('Poll get_publication for progress'), which tells the agent both when to invoke and what to do next. It stops short of explicit when-not-to-use guidance, e.g. when to prefer cancel_publication or update_publication instead.

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