cancel_post
Cancel a scheduled post before it publishes.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| postId | Yes |
socialclaw
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry behavioral disclosure. It discloses the timing constraint ('before it publishes') but does not describe side effects, idempotency, or error cases.
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?
Single clear sentence, front-loaded with the action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and an undocumented parameter, the description is too thin. It lacks information about outcomes, errors, or prerequisites.
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 has one parameter with no description, and schema coverage is 0%. The description does not explicitly define postId, though it's implied. It fails to compensate for the missing schema documentation.
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 clearly states the tool cancels a scheduled post, using a specific verb and resource. It is distinct from siblings like publish_draft or retry_post.
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?
Provides clear context that this applies to scheduled posts before publishing, but does not explicitly mention alternatives or when not to use it.
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.
TDQS
B3.4/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, but a few are close: delete_instagram_comment vs hide_instagram_comment overlap (though one is preferred), and get_analytics overlaps with Instagram-specific analytics tools. Overall, the boundaries are generally clear, with only minor potential confusion.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_accounts, connect_account, upload_asset, cancel_post). There are no deviations in style or grammar, making the naming highly predictable.
Tool Count2/5
With 31 tools, this exceeds the 25-tool threshold for 'too many'. While the broad multi-provider social media domain justifies some breadth, the sheer number makes the surface heavy and potentially overwhelming, pushing the score down.
Completeness4/5
The tool set covers core workflows well: account connection, scheduling/publishing, post management, analytics, Instagram-specific engagement (comments, messages), asset upload, and workspace health/usage. Minor gaps include no explicit disconnect_account or delete_post, but these are edge cases; the domain is largely covered.