Skip to main content
Glama

Eurekuh

Cancel a post

cancel_post
Destructive

Delete a post that has not gone out — a draft, a scheduled post, or a failed one. A post that is already published cannot be cancelled here; it has to be deleted on the network.

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_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
organizationIdNoWhich organization to act in: an id from list_organizations. Leave out for this connection's default organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the mutation profile is covered. The description adds the useful precondition on post state, but does not state whether cancellation is reversible, what happens to scheduling metadata, or what a repeat call on an already-cancelled post does (relevant given idempotentHint=false).

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?

Two tight sentences, front-loaded with the operation and its state constraint, then the exclusion. No filler, and every clause carries information an agent would otherwise have to guess.

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?

Covers what the tool does and the key precondition, which is the main risk with a destructive operation. It omits whether the deletion is permanent, what the call returns, and how an already-published post should be handled via a sibling, leaving gaps for a non-idempotent destructive tool with 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?

Only organizationId carries schema documentation (an id from list_organizations); the required id parameter has no schema description, putting coverage at 50%. The description adds no meaning to either parameter, so it neither compensates for the gap nor strengthens the documented one. Baseline 3 for a partially documented two-parameter schema.

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 (delete/cancel) and resource (post) and narrows scope to unpublished states: draft, scheduled, or failed. It never names a sibling tool, so the agent must infer that update_post or get_post_status are the alternatives, but the state qualifier still makes the purpose distinguishable.

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 clear when-to-use cases (draft, scheduled, failed) and an explicit when-not (already-published posts cannot be cancelled here). The alternative it offers is 'delete on the network' rather than a sibling tool, so the routing guidance is directional but not actionable within this server.

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