Skip to main content
Glama

cancel_scheduled_post

DestructiveIdempotent

Cancel a not-yet-published post (draft, scheduled, or failed) and permanently delete it, tearing down its EventBridge schedule if it has one. Refuses to touch a post that has already published or is mid-publish — this cannot un-publish something already on Instagram.

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_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
workspace_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 idempotentHint=true, so the safety profile is known. The description goes beyond them by disclosing what is destroyed (the post permanently, plus its EventBridge schedule) and by documenting a guard behavior the annotations do not encode — refusal on already-published or in-flight 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?

Two sentences, front-loaded with the action and effect, then the guard condition. No filler; every clause adds information an agent needs.

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?

An output schema exists so return values need no explanation, and the mutation semantics, side effects, and preconditions are covered. The only gap is parameter meaning, minor given simple, clearly named identifiers.

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% for both required parameters, so the description carries the burden of explaining them — and it says nothing about post_id or workspace_id (e.g., whether workspace_id is needed for scoping or permission, or whether an already-cancelled post errors or no-ops). The parameter names are largely self-explanatory, which keeps this above a 1.

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?

Specific verb ('cancel') plus resource ('a not-yet-published post') plus the eligible states (draft, scheduled, failed) and the resulting effect (permanent delete). An agent can immediately distinguish this from update_scheduled_post, list_scheduled_posts, or retry_failed_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?

Explicitly states the exclusion: it refuses posts already published or mid-publish, and explains why ('cannot un-publish something already on Instagram'). It does not name a sibling to use instead for non-cancellable cases, so it stops short of full alternative routing.

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