PostOnce

cancel_post

Destructive

Cancels a scheduled or still-pending post without deleting its aggregate record or already published social content.

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

Name	Required	Description	Default
`id`	Yes
`idempotency_key`	No

Output Schema

Name	Required	Description
`body`	No	Upstream error details, when available.
`code`	No	Error code when the tool result has isError=true.
`data`	No	Present on successful results; omitted on tool errors.
`meta`	No
`status`	No
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations establish a destructive, non-read-only operation, while the description adds important scope: the aggregate record and already published social content survive. It does not further explain retry behavior or outcomes for partially published or ineligible posts.

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?

One front-loaded sentence communicates the action, eligible states, and two preservation guarantees without filler. Its length is appropriate for a simple two-parameter operation.

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 low-complexity cancellation tool with an output schema and clear safety annotations, the definition supplies the key state and preservation semantics needed for invocation. Undocumented parameters and unspecified handling of ineligible post states keep it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not document either parameter. The `id` can be inferred to identify the target post, but no format or lookup guidance is given, and the purpose and reuse semantics of `idempotency_key` are unexplained.

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?

The description uses a specific verb and resource and limits the operation to scheduled or still-pending posts. The clause about preserving the aggregate record and already published social content also distinguishes cancellation from deletion or content removal.

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?

The state qualifier tells the agent when cancellation applies, providing meaningful selection guidance. It does not explicitly address already published, failed, or otherwise ineligible posts, or name an alternative tool for those cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PostOnce tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?