xpost

Delete a post

delete_post

DestructiveIdempotent

Remove a post this key created that has not gone out. A draft, a post waiting for approval, a rejected or a failed one is deleted with its delivery records. A post already holding a time is taken off the schedule instead, and unscheduled with message says so. Posts a person approved are refused, and so is one that has gone out — removing THAT from the platform is take_down_post.

Input Schema

Name	Required	Description	Default
`post_id`	Yes	The post id from create_post

Output Schema

Name	Required	Description
`id`	No
`ok`	No	Present and false only on a refusal.
`error`	No	What was refused, in a sentence, when `ok` is false.
`status`	No
`deleted`	No	Gone permanently, with its delivery records.
`message`	No
`retriable`	No	False when asking again cannot change the answer.
`error_code`	No	Machine reason for a refusal.
`replaced_by`	No	The id the post has now, when you asked with one an edit retired. An edit gives a post a new id: get_delivery_receipt and get_post_metrics answer for this current version (and `asked_for` is the id you sent); update_post and delete_post refuse with error_code `replaced`. Use this id from here on.
`unscheduled`	No	Taken off the schedule and handed back to the user instead of deleted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / properties / replaced_by / description

Previous value: -"With error_code `replaced`: the id the post has now. An edit gives a post a new id; use this one."New value: +"The id the post has now, when you asked with one an edit retired. An edit gives a post a new id: get_delivery_receipt and get_post_metrics answer for this current version (and `asked_for` is the id you sent); update_post and delete_post refuse with error_code `replaced`. Use this id from here on."

Changed1 schema field changedOct 2, 2026

addedOutput schema / properties / replaced_by

Added value: +{
+  "description": "With error_code `replaced`: the id the post has now. An edit gives a post a new id; use this one.",
+  "type": "string"
+}

First observedSep 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations declare destructive/idempotent, but the description goes well beyond them: it discloses cascading deletion of delivery records, the non-obvious branch where a scheduled post is unscheduled instead of deleted, and the return signal (`unscheduled` with `message`). It also spells out which posts are refused and why, which an agent cannot infer from the schema.

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?

Highly information-dense with the primary constraint front-loaded and no filler. Some clauses are telegraphic ("a rejected or a failed one is deleted with its delivery records"), which costs a little readability but every sentence carries distinct behavioral 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?

An output schema exists, so return shape needn't be explained, yet the description still flags the `unscheduled`/`message` response case. For a single-parameter destructive tool, the destructive scope, cascade effects, refusals, and the alternative path are all covered.

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?

Only one parameter, `post_id`, and schema coverage is 100% with a usable description ("The post id from create_post"). The prose adds no additional meaning about the identifier beyond that, so this sits at the baseline where the schema does all the work.

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 ("Remove a post") plus a precise scope: posts this key created that have not gone out. It explicitly distinguishes itself from the sibling take_down_post for posts that have already published, so an agent can route without opening either 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?

Enumerates the eligible states (draft, awaiting approval, rejected, failed) and the two refusal cases (human-approved, already published), naming the alternative tool for the latter. The when-not guidance is explicit and actionable.

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

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