Skip to main content
Glama

Cancel a scheduled post

cancel_post
DestructiveIdempotent

Cancels a scheduled post that has not gone out yet. Only after the user agreed.

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": {
      "post_id": "<post_id>"
    },
    "name": "cancel_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so safety is covered. The description adds real value by restricting eligibility to posts that have not yet published and requiring user consent, but it never says what happens on cancel (permanent deletion vs. unscheduling), whether it can be undone, or how an already-published post is rejected.

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?

Two short sentences, front-loaded with the action and then the constraint; nothing is wasted. The second sentence is a fragment that reads slightly tersely but still earns its place as a precondition.

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

Completeness3/5

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

For a destructive one-parameter mutation with no output schema, the definition covers eligibility and consent but omits the post-cancel state, failure behavior for already-published posts, and any notion of what the caller receives. Annotations carry the safety profile, so the gap is moderate rather than severe.

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 0% for the single post_id parameter, so the description must carry the burden. It does add meaning by constraining which post_id is valid (must reference a scheduled, unpublished post), but it never clarifies the identifier format or where the agent obtains it, which the regex pattern alone does not explain.

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?

States a specific verb and resource ('Cancels a scheduled post') plus an eligibility constraint ('has not gone out yet'), which separates it from publish_post and reschedule_post by implication. It does not name a sibling explicitly, so it stops short of a 5.

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

Usage Guidelines3/5

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

The 'only after the user agreed' clause is a consent gate rather than routing guidance, and there is no explicit statement of when to cancel versus reschedule or otherwise edit. The eligibility phrase ('not gone out yet') implies usage context but leaves the alternative unaddressed.

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.