Skip to main content
Glama

Delete draft

delete_draft

Delete a post that is still a draft, whether it was created in the Flomixy app or through the API. Scheduled, paused, publishing and failed posts cannot be deleted (409), and neither can published ones unless the environment is a dev/staging one that allows it; in that case the published post is also removed from each network and the result lists the outcome per network. Requires scope POSTS_DELETE, which is only offered to members allowed to delete posts. Check the post with get_post first: posts with the same caption on different networks are separate drafts, not duplicates.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe draft post id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses the required scope POSTS_DELETE, the 409 error for non-draft states, the exception for dev/staging environments, and the cascade that removes the post from each network with per-network outcomes. It stops short of stating permanence/irreversibility or any rate-limit behavior.

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?

Front-loaded with the core action and then layered with exclusions, auth, and a prerequisite tip. Dense but every clause carries operational meaning; the final get_post sentence is slightly tangential to deletion itself but prevents duplicate-draft confusion.

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 mutating tool with no annotations and no output schema, this covers scope, failure state, environmental exception, and response shape (per-network outcomes). The main omissions are whether deletion is permanent and what a normal successful response contains for the non-published case.

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 100% for the single `id` parameter, so the baseline is 3. The description adds real semantics on top: the note that identical captions on different networks are separate drafts clarifies that the id identifies one network-specific draft, not a logical duplicate group.

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 tightly scoped resource: 'Delete a post that is still a draft', including drafts created via app or API. It immediately distinguishes this from deleting published posts and from other post-mutation siblings by naming the exact status boundary (draft only).

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?

Enumerates the statuses that are not deletable (scheduled, paused, publishing, failed → 409) and gives a prerequisite step, 'Check the post with get_post first'. It does not explicitly route to a sibling for published posts, leaving slight ambiguity with delete_post, but the when/when-not conditions are unusually explicit.

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