Skip to main content
Glama

delete_post

Destructive

Permanently delete a post from DemandBird, with its comments, reviews, sources and version history. It cannot be undone. A scheduled post is refused: unschedule it with cancel_post first. A post already published stays live on the platform; this only removes DemandBird's copy. Only the post's author or an account admin may delete it. To keep a post but stop it going out, use cancel_post. To park it, use update_draft with stage on_hold.

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
idYesPost ID to delete
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description goes well beyond that: irreversibility, cascading deletion of comments/reviews/sources/version history, refusal on scheduled posts, the fact that a published post stays live on the external platform (only the DemandBird copy is removed), and the authorization rule (author or account admin). That is exactly the context an agent needs before calling a destructive tool.

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?

Destructiveness and irreversibility are front-loaded in the first two sentences, then refusal conditions, then side effects, then permissions, then alternatives. Every sentence carries a distinct operational fact with no 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 two-parameter destructive tool with no output schema, the description covers the safety profile, failure mode, external side effects, and permissions. Nothing an agent needs in order to invoke it correctly is missing.

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% and both fields are self-documenting, so the schema does the work. The description adds no meaning about the id or the workspace override, leaving this at the baseline for fully-documented schemas.

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 precise verb+resource ('Permanently delete a post') and enumerates the cascade scope (comments, reviews, sources, version history). It explicitly separates itself from cancel_post and update_draft, so an agent can pick it out of a crowded sibling list without opening schemas.

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: scheduled posts are refused and must be unscheduled via cancel_post; to simply stop a post going out use cancel_post; to park it use update_draft with stage on_hold. Alternatives and their selecting conditions are named outright.

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