postmoderno

Delete post

delete_post

DestructiveIdempotent

Delete a post that has not started going out: a draft, or one that is scheduled, canceled, held (plan_hold) or failed. A scheduled post is called off and deleted in one step. Deleting the root of a chain deletes its replies; deleting a reply removes only that reply, and the replies after it move up a place. A reply in a scheduled chain cannot be deleted on its own until the chain is canceled. Attachments are removed from storage too. Deleting a post that is already deleted succeeds again, so a retry is safe.

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

Input Schema

Name	Required	Description	Default
`post_id`	Yes	the post id

Output Schema

Name	Required	Description	Default
`status`	Yes
`post_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavioral details: deleting a root deletes replies, deleting a reply shifts later replies up, scheduled-chain replies have a special restriction, attachments are removed from storage, and retries are safe because deleting an already-deleted post succeeds. This is exactly the kind of context the destructive and idempotent hints cannot convey alone.

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?

The description is front-loaded with the core action and eligibility rule, then adds only behaviorally relevant details about cascading deletion, reply ordering, scheduled-chain restrictions, attachments, and retry safety. Every sentence earns its place for a destructive operation with these edge cases.

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?

Given a destructive delete tool with one parameter, complete annotations, and an output schema, the description covers eligibility, cascading effects, special restrictions, attachment cleanup, and idempotency. An agent has enough information to call it correctly and understand the consequences.

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 the single parameter post_id is already documented in the schema as 'the post id.' The description adds no further meaning about the identifier format, source, or constraints, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource, 'Delete a post,' and immediately scopes it to posts that have not started going out: drafts, scheduled, canceled, held, or failed. This level of specificity lets an agent distinguish deletion from other post lifecycle operations without opening the schema.

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?

The description clearly states which post states are eligible for deletion and gives an explicit exclusion: a reply in a scheduled chain cannot be deleted on its own until the chain is canceled. It does not explicitly name cancel_post as the alternative when the goal is to cancel without deleting, though that distinction is implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All postmoderno tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?