Skip to main content
Glama

Delete a post

flypost_delete_post
Destructive

Permanently delete a post: its concept (with its slides and images) and its drafts, as the app's Delete does. Pass draft_id, or content_bank_item_id for a concept. Refused for a post that is scheduled, publishing or published (cancel a scheduled one first with flypost_cancel_scheduled_post). Only when the user asks; to drop an unwanted idea use flypost_discard_idea.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flypost_delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idNo
content_bank_item_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the details that matter: permanence, exactly what is destroyed (concept, slides, images, drafts), and which post states cause refusal. That is behavior beyond what the annotations convey and it directly prevents destructive misfires.

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 short sentences, front-loaded with the destructive action and its scope, then parameter selection, then refusal conditions, then the policy gate and alternative. No filler or redundancy.

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 two-param destructive tool with no output schema, the definition covers scope of destruction, failure states, remediation path, and the correct sibling for the adjacent intent. Nothing an agent needs before invoking it is missing.

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 0%, so the description must carry parameter meaning, and it does: it explains that draft_id targets a draft while content_bank_item_id targets a concept, and the 'or' implies they are mutually exclusive selectors. It does not clarify that neither is schema-required nor what an invalid ID returns, so it falls just short of fully compensating.

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 and resource ('Permanently delete a post') plus the exact blast radius (the concept with its slides and images, and its drafts). The phrase 'as the app's Delete does' anchors it to a known UI behavior, so an agent can distinguish it from discard/archive siblings immediately.

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-not conditions (refused for scheduled, publishing or published posts), the recovery path ('cancel a scheduled one first with flypost_cancel_scheduled_post'), a policy gate ('Only when the user asks'), and the correct alternative for a different intent ('to drop an unwanted idea use flypost_discard_idea').

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.