Skip to main content
Glama

Cancel a scheduled post

cancel_post
DestructiveIdempotent

Unschedules a post that has not started publishing, as the app's Cancel does: it goes back to APPROVED when the workspace requires approval or a reviewer approved it (schedule_post again, no new approval needed), otherwise to DRAFT.

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": {
      "workspace_id": "<workspace_id>",
      "post_id": "<post_id>"
    },
    "name": "cancel_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
workspace_idYesWorkspace id from list_workspaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real context beyond the annotations: the exact resulting status (APPROVED vs DRAFT) depending on workspace approval rules, and that no new approval is required on reschedule. It does not state what happens if the post already started publishing (error vs no-op), and it doesn't reconcile the destructiveHint=true with what reads as a reversible state revert.

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?

One dense but well front-loaded sentence; the key precondition and outcome come first. The parenthetical clause about approval is slightly run-on but every clause carries information.

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 two-parameter mutation with no output schema, the description covers the state machine and the reschedule path, which is the non-obvious part. Missing only failure/edge behavior for the already-publishing case and any mention of what the call returns.

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 coverage is 50%: workspace_id is described (from list_workspaces) but post_id has no description in either schema or description text. The description says nothing about parameter meaning, formats, or how to obtain a post_id, so it fails to compensate for the coverage gap.

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 (unschedules) plus resource (a post) and a precondition (has not started publishing), which separates it from delete_post and update_post. The mention of schedule_post for resuming further anchors it against siblings.

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 a clear use condition (only for posts that haven't begun publishing) and points to the follow-up tool (schedule_post again) when the user wants to reschedule. It doesn't name what to use instead when the post is already publishing or when the user really wants deletion, so exclusions are incomplete.

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