Ravenpost

Delete a post

delete_post

DestructiveIdempotent

Permanently delete Ravenpost’s copy of a post and cancel any scheduled publish — the post cannot be restored. Use this to remove drafts or duplicate/obsolete scheduled posts. It never takes a post down from a network: a post already published stays live on the platform. The dashboard offers a separate "delete everywhere" on the networks Ravenpost can delete from (a post on Instagram, TikTok, Threads and YouTube cannot be taken down through Ravenpost at all); this tool does not.

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

Input Schema

Name	Required	Description	Default
`postId`	Yes	The post id to delete

Output Schema

Name	Required	Description	Default
`ok`	No
`deleted`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds critical context beyond them: irreversibility ('cannot be restored'), the side effect of cancelling scheduled publishes, and the platform limitation that Instagram/TikTok/Threads/YouTube posts cannot be removed at all. This directly prevents a dangerous misassumption about what 'delete' means here.

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?

The destructive/permanence warning is front-loaded, which is the right ordering. The final two sentences overlap somewhat ('never takes a post down from a network: a post already published stays live' versus 'delete everywhere' / network list), costing a little tightness, though the platform list is genuinely useful information.

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?

With one required parameter, an existing output schema, and rich annotations, the description covers everything an agent needs: what is destroyed, side effects, reversibility, and the common misuse case. Nothing material is left unspecified.

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?

There is a single parameter (postId) with 100% schema description coverage, so the schema already carries its meaning. The description adds no format, source, or provenance detail for the id (e.g., where to obtain it), so the 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 and resource ('Permanently delete Ravenpost's copy of a post') plus the side effect ('cancel any scheduled publish'), and explicitly distinguishes the scope from sibling operations like publish_post/update_post by ruling out network removal. An agent can tell exactly what this destroys 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 Guidelines5/5

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

Names the intended cases ('remove drafts or duplicate/obsolete scheduled posts') and the excluded case ('never takes a post down from a network'), and points to the alternative mechanism ('The dashboard offers a separate "delete everywhere"'). Both when-to-use and when-not-to-use are explicit.

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

All Ravenpost 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.