Delete a post
bluesky_delete_postPermanently delete a specific Bluesky post using its at:// URI.
Instructions
Permanently delete one of your own posts.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uri | Yes | at:// URI of the post to delete. |
bluesky_delete_postPermanently delete a specific Bluesky post using its at:// URI.
Permanently delete one of your own posts.
| Name | Required | Description | Default |
|---|---|---|---|
| uri | Yes | at:// URI of the post to delete. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the irreversibility ('Permanently') and ownership constraint ('your own posts'), which are critical for an agent to understand the tool's side effects and authorization requirements.
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?
A single sentence that is concise and front-loaded, with no wasted words. It conveys the action, permanence, and scope efficiently.
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 simple one-parameter deletion tool with no output schema and no annotations, the description is complete. It covers what, the permanence, and the ownership requirement, leaving no critical gaps for an agent to function 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 input schema already provides 100% parameter coverage, including a clear description for the 'uri' parameter. The tool description does not add further semantic detail, so the baseline score of 3 is appropriate.
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 resource ('your own posts'), clearly distinguishing it from sibling tools like like, repost, or follow. It immediately tells the agent exactly what action is performed.
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 phrase 'your own posts' provides essential usage context, clarifying that only the authenticated user's posts can be deleted. It does not explicitly name alternatives, but none are needed since this tool is unique among siblings for deleting posts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AhmadTariq1337/bluesky-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server