Posteady

Cancel scheduled post

cancel_scheduled_post

Destructive

Cancel a pending scheduled post (cancels the whole thread chain if it is part of one). TikTok Business, Instagram, YouTube, and Facebook cancellation affect only the selected draft and are allowed until processing starts. The target workspace is determined automatically from the scheduledPostId.

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": {
      "scheduledPostId": "<scheduledPostId>",
      "platform": "<platform>"
    },
    "name": "cancel_scheduled_post"
  }
}

Input Schema

Name	Required	Description
`platform`	Yes	Platform of the scheduled post (shown in list_scheduled_posts).
`workspaceId`	No	Optional. The target workspace is determined automatically from the scheduled post. When given, it must match the post's workspace.
`scheduledPostId`	Yes	ID from list_scheduled_posts.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, and the description earns credit by quantifying the blast radius: the entire thread chain is cancelled for chained posts, whereas other platforms affect only the selected draft. It also discloses the timing constraint before processing begins and that workspace targeting is implicit.

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?

Three tight sentences, front-loaded with the action and its most consequential side effect. The platform sentence is slightly muddled by naming 'TikTok Business' while the enum value is 'tiktok', a small ambiguity that costs a point.

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 3-parameter mutation tool with full schema coverage and no output schema, the description covers scope, timing, and targeting adequately. It leaves unclear what a successful cancellation returns or whether the operation is idempotent for an already-cancelled post.

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 description coverage is 100%, so all three parameters are already documented, including the workspaceId auto-resolution rule. The description restates the workspace behavior from scheduledPostId but adds no new format, constraint, or edge-case detail beyond the schema.

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 ('Cancel a pending scheduled post') and immediately qualifies scope: whole thread chain for thread-based platforms, single draft for TikTok/Instagram/YouTube/Facebook. An agent can distinguish this from schedule_post or publish_post without opening 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 Guidelines4/5

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

Provides a clear applicability window ('allowed until processing starts'), which tells the agent when the call will fail. It does not name a sibling alternative for posts already processing (e.g., checking get_publish_status instead), so it stops short of full when-not/alternatives guidance.

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

All Posteady 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?