Skip to main content
Glama

Cancel a scheduled publication or draft

cancel_publication
Destructive

Cancel a scheduled publication, or delete a draft, before it is published. It is never published and its kept media is deleted, so confirm with the user first. Fails once the publication has started.

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": "cancel_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.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes further: it says the item is never published, that kept media is deleted, and that the call fails after publication starts. The explicit 'confirm with the user first' instruction is a meaningful guardrail for an irreversible action.

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?

Three short sentences, front-loaded with the action before the caveats, and no filler. The phrase 'its kept media' is slightly ambiguous, but nothing is wasted.

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?

For a one-parameter destructive tool with full schema coverage and no output schema, the description supplies everything an agent needs: what it destroys, the irreversibility, the timing limit, and the confirmation requirement.

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 already carries a description pointing to create_publication or list_publications as the source. The description adds no additional meaning about the id itself, so this sits at the baseline for a fully documented parameter.

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 ('Cancel') plus two concrete resource cases (scheduled publication, draft), and scopes it with 'before it is published'. This is immediately distinguishable from siblings like publish_publication or get_publication.

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 a clear usage window ('before it is published') and an implicit boundary condition ('Fails once the publication has started'), which tells the agent when the tool won't work. It does not name a sibling alternative, but the pre-publication scope makes the choice obvious.

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