Skip to main content
Glama

Delete scheduled post

delete_post

Delete a draft, scheduled or paused post that was created through the API, cancelling its pending publish. Refused with 409 when the post was created in the Flomixy app, or when any network target is already published or publishing. It never deletes anything on a social network. Use delete_draft for app-created drafts. Requires scope POSTS_WRITE.

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": {
      "id": "<id>"
    },
    "name": "delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe draft, scheduled or paused post id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so: it explains that pending publish is cancelled, that nothing is removed on the social network, the exact 409 refusal conditions, and the required POSTS_WRITE scope. This is precisely the context an agent needs before invoking a destructive operation.

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?

Four compact sentences, front-loaded with the action and scope, then refusal conditions, then the non-effect, then the sibling alternative and auth requirement. No sentence is filler.

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 one-parameter destructive tool with no annotations and no output schema, the description covers the action scope, failure modes, side-effect boundaries, permissions, and alternative tool. There is no material gap an agent would need to call it correctly.

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 coverage is 100%, so the single `id` parameter is already documented as the draft, scheduled or paused post id. The description restates the same accepted states without adding format, sourcing, or lookup guidance beyond the schema, so baseline 3 applies.

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 (delete) and resource (draft, scheduled or paused post created through the API), and narrows scope in a way an agent can act on. It also explicitly differentiates from delete_draft by pointing app-created drafts at that tool.

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

Usage Guidelines5/5

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

Gives explicit when-to-use and when-not-to-use rules: only API-created posts, refused with 409 for app-created posts or already-published/publishing targets, and names delete_draft as the alternative for app-created drafts. Nothing about routing 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