Skip to main content
Glama
Sign In
x-mcp

x-mcp

by rthomas24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete one of your posts

delete_post
DestructiveIdempotent

Remove a post you authored from X (Twitter). Confirmation is required; deletion is permanent and removes the entire edit chain. Override ownership checks with force, but this triggers human approval.

Instructions

Delete a post you authored (only posts this server knows as yours, unless force=true). Irreversible; in approval mode it is queued for the human. Cost $0.01. Deleting any version of an edited post deletes the whole edit chain.

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

Input Schema

NameRequiredDescriptionDefault
forceNoAllow deleting a post id not recorded by this server. Always requires human approval.
confirmYesMust be true — deletion is irreversible.
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds important details beyond annotations: irreversible action, cost ($0.01), approval queue behavior, and the whole edit chain deletion. These are not present in the readOnly/destructive/idempotent hints.

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?

Three concise sentences, front-loaded with the purpose, and each sentence adds distinct information without redundancy.

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 the tool's simplicity and lack of output schema, the description covers all relevant aspects: scope, force behavior, approval, cost, irreversibility, and edit chain effects, leaving no major gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers force and confirm with descriptions, but post_id has no description and the tool description does not clarify it. Since schema coverage is only 67% (below 80%), the description fails to compensate for the missing parameter detail.

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?

Clearly states the action: 'Delete a post you authored' and specifies the scope (only posts the server knows as yours, with a force option). Distinguishes from sibling tools by focusing on deletion rather than publishing, reposting, or messaging.

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?

Provides conditional guidance (force for posts not recorded, approval mode queues for human) and mentions cost. Lacks explicit alternatives, but the context of deleting authored posts makes usage clear.

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

Deploy Server

Other Tools