Statuz

Delete post

posts_delete

DestructiveIdempotent

Delete a post: from the platforms it went out to, then from Statuz. Every published part of the thread is deleted on its platform first. If a platform refuses, the post stays in Statuz with only what is left, so deleting again retries it.

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": "posts_delete"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`org`	No	Org id (default: your first org)
`keepOnPlatforms`	No	Only delete it from Statuz; published copies stay up

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds real behavior beyond annotations: platform-first ordering, partial-failure state (post stays with only what's left), and that re-running retries remaining platform deletions. Doesn't mention permissions or whether the Statuz record's id/history is retained after full success.

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?

Three short sentences, front-loaded with the core action and ordering. Minor awkwardness in the opening 'Delete a post: from the platforms...' construction, but nothing is wasted.

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?

No output schema and annotations already flag destructive/idempotent, so the description's job is failure semantics, which it covers well. It omits what a successful call leaves behind and doesn't touch the two optional params.

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 67% and both optional params already carry descriptions; the description explains the default platform-delete behavior but never names keepOnPlatforms or org, so it adds only marginal meaning over the schema.

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 (delete) and resource (post) plus the exact scope: platform copies first, then the Statuz record. That two-tier scope cleanly separates it from neighbors like posts_edit or media_remove.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

No explicit when-to-use/when-not guidance or named alternatives (e.g. posts_edit for content changes, keepOnPlatforms for unpublishing only). Usage is implied by the deletion ordering, and the retry note acts as a partial recovery guideline.

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

All Statuz 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?