Skip to main content
Glama

Cancel a scheduled post

flypost_cancel_scheduled_post
Destructive

Unschedule a previously scheduled LinkedIn post — deletes it at the provider and reverts the draft to editable.

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": {
      "draft_id": "<draft_id>"
    },
    "name": "flypost_cancel_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the mutation and external side effects are known before reading the description. The description still earns credit by specifying two concrete consequences beyond the annotations: deletion at the provider, and the draft reverting to an editable state, which tells the agent the action is recoverable. It omits failure modes and whether the provider deletion is irreversible.

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?

A single front-loaded sentence with the action first and the consequences second; every clause carries information. It is efficient, though a brief precondition clause would have fit without bloat.

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 one-parameter destructive tool with no output schema, the description covers the essential facts: what gets deleted, where, and what state the draft ends in. The remaining gap is identifying which drafts are valid inputs and what happens on provider failure.

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?

There is a single required parameter at 0% schema description coverage, so neither the schema nor the description explains what draft_id refers to (a scheduled draft versus any draft). The name is largely self-explanatory, but the description adds no meaning beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (unschedule) and resource (a previously scheduled LinkedIn post), plus the resulting state change, so it is clearly distinguishable from flypost_schedule_post. It stops short of naming any sibling tool explicitly, which keeps it at a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The word 'previously scheduled' implies the precondition that the post must already be scheduled, and the revert-to-editable outcome hints that the draft remains usable afterwards. However, it never says what to do for a post that was never scheduled or already published, and it names no alternative tool for those cases.

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.