AT Protocol MCP Server

delete_post

Destructive

Permanently delete a post from your AT Protocol repository using its AT-URI. This irreversible action removes content you no longer want.

Instructions

Delete a post on AT Protocol. Permanently removes the post from the authenticated user's repository; this action cannot be undone. Use this instead of create_post/reply_to_post when you need to remove existing content. Requires authentication (app password). Subject to per-tool rate limiting.

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

Input Schema

Name	Required	Description	Default
`uri`	Yes	AT-URI of the post to delete (at://did/app.bsky.feed.post/rkey). Must belong to the authenticated user.

Output Schema

Name	Required	Description
`success`	Yes	Whether the post was successfully deleted.
`message`	Yes	Human-readable result message.
`deletedPost`	Yes	Information about the deleted post.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.2Jun 23, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed2 schema fields changedv0.6.0Jun 11, 2026

addedInput schema / properties / uri / description

Added value: +"AT-URI of the post to delete (at://did/app.bsky.feed.post/rkey). Must belong to the authenticated user."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "deletedPost": {
+      "description": "Information about the deleted post.",
+      "properties": {
+        "uri": {
+          "description": "AT-URI of the deleted post.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "uri"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable result message.",
+      "type": "string"
+    },
+    "success": {
+      "description": "Whether the post was successfully deleted.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "message",
+    "deletedPost"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.3.0Jun 9, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedv0.2.1Jun 2, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Reinforces destructiveHint by noting 'Permanently removes... cannot be undone'. Adds context about authentication and rate limiting not covered by annotations. No contradiction.

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?

Two short, front-loaded sentences with no waste. First sentence states purpose, second provides usage and behavioral context.

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?

Complete given the simple input (1 required param with full schema coverage) and presence of output schema. Covers purpose, usage, behavior, and constraints.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds the constraint that the URI must belong to the authenticated user, providing extra clarity beyond the schema's description.

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 'Delete a post on AT Protocol', specifying the verb and resource. Distinguishes from siblings like create_post and reply_to_post by noting its use for removal.

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?

Explicitly states 'Use this instead of create_post/reply_to_post when you need to remove existing content', providing clear when-to-use guidance. Also mentions authentication and rate limiting.

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