Remove a Bluesky post by providing its AT URI. Use this to delete unwanted posts directly from your account.
Delete a Bluesky post by AT URI
| Name | Required | Description | Default |
|---|---|---|---|
| uri | Yes | AT URI of the post to delete |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description has the full burden of disclosing behavioral traits. While 'Delete' signals a destructive action, the description does not state that the deletion is permanent, that the caller must own the post, or that associated interactions (likes/reposts/replies) may be affected. It only restates the operation, adding little beyond the tool name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence that names the action and target with no filler. It is concise and every word contributes to the meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive mutation tool with no annotations and no output schema, the description is thin. It correctly identifies the required input but omits important surrounding context such as ownership, irreversibility, and expected result/error behavior, which an agent would need to invoke it safely and correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the only parameter, 'uri', as 'AT URI of the post to delete' (100% coverage), so the description's mention of 'AT URI' adds no new meaning. The baseline of 3 applies because the schema fully describes the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Delete') and a clear resource ('Bluesky post'), and identifies the required address ('AT URI'). This is unambiguous and distinct from sibling tools such as create_post, like_post, or get_post, which involve creation, reaction, or reading.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description defines what the tool does but gives no explicit when-to-use or when-not-to-use guidance, and does not mention the ownership prerequisite (you can only delete your own posts). Among the sibling tools there is no other deletion tool, so the usage context is inferable, but not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.