Skip to main content
Glama

Cancel a scheduled post

clipember_cancel_scheduled_post
DestructiveIdempotent

Cancel a draft, queued, failed or unconfirmed post (clip or own video). Set wholeGroup=true to cancel every platform created by the same clipember_create_post call. A post that already went out cannot be canceled — it has to be deleted on the platform itself. repeatStopped=true in the result means you canceled the last live post of the latest group of an active repeat, so the repeat stops too (no more posts are created) — tell the user; to keep repeating, create a new repeat.

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": {
      "postId": "<postId>"
    },
    "name": "clipember_cancel_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYes
wholeGroupNoAlso cancel the other platforms of the same post group

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / wholeGroup
      Added value: +{
      +  "default": false,
      +  "description": "Also cancel the other platforms of the same post group",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, yet the description goes well beyond them: it discloses the cascading scope of wholeGroup, the irreversible nature of missing the cancel window, and the non-obvious repeatStopped side effect that terminates an active repeat. That repeat-termination warning is exactly the kind of latent consequence an agent must surface to a user.

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?

Front-loaded with the action and the eligible states, then layered constraints. The repeatStopped sentence is long but every clause (result flag, cause, instruction to tell the user, recovery path) carries decision-relevant information, so it earns its length.

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

Completeness5/5

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

For a destructive two-parameter tool with no output schema, the description covers eligibility, group scope, the failure mode for already-published posts, and even the repeatStopped field it returns. There is no material gap an agent would need to guess at before calling it.

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

Parameters4/5

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

Schema coverage is only 50% and postId carries no prose at all, but its UUID format makes it self-evident. The description meaningfully expands wholeGroup beyond the schema's 'also cancel the other platforms of the same post group' by tying the group to a specific clipember_create_post call, clarifying what 'group' means and how it spans platforms.

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 opens with a specific verb and resource plus the exact set of states it applies to ('Cancel a draft, queued, failed or unconfirmed post (clip or own video)'), and immediately carves out the case it does not cover (already-published posts). An agent can tell exactly what this does without opening the 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?

It gives a clear when-not rule: a post that already went out cannot be canceled and must be deleted on the platform itself, and it explains the wholeGroup escalation path. It stops short of naming sibling alternatives such as reschedule or retry for a post that hasn't gone out yet, so routing to another tool is left to inference.

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