Skip to main content
Glama

Cancel a scheduled post

cancel_schedule
DestructiveIdempotent

Cancels a scheduled post by id. A post that is being published right now answers 409 publishing_in_progress. A cancelled post drops out of list_schedules. There is no way to move a scheduled time: cancel it and schedule again. Applies when the user no longer wants a scheduled post to go out.

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": "cancel_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, and readOnly=false, so the safety profile is covered. The description still adds real value beyond them: the 409 publishing_in_progress failure mode for a post mid-publish, and the observable side effect that a cancelled post drops out of list_schedules. It stops short of stating irreversibility in so many words, but 'no way to move a scheduled time' implies the consequence.

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?

Four short sentences, each carrying a distinct fact: the action, the conflict error, the visible side effect, and the missing-reschedule workaround, with the trigger condition last. 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 with no output schema, the description covers the failure mode and the post-condition (removal from list_schedules), which is what an agent needs to call it and report back. Only the exact return payload or confirmation shape is left unspecified, a minor gap given there is no output schema.

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?

With a single required parameter at 100% schema coverage, the schema already documents 'id' as the post id, and the description only restates 'by id'. No format, source, or lookup guidance is added, so this sits at the baseline.

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 ('Cancels a scheduled post by id') and implicitly scopes it against list_schedules and schedule_text by naming the list it removes the item from. An agent can tell this apart from scheduling or listing tools without inspecting any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Applies when the user no longer wants a scheduled post to go out') and an explicit alternative workflow for the adjacent intent: 'There is no way to move a scheduled time: cancel it and schedule again.' That closes the most likely routing ambiguity for a cancel tool.

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.