AT Protocol MCP Server

unrepost

Destructive

Delete a repost record on the AT Protocol using its AT-URI, undoing a previous repost action. Requires authentication.

Instructions

Remove a repost on AT Protocol. Deletes the repost record owned by the authenticated user, undoing a previous plain repost; this action cannot be undone without re-calling repost. Requires authentication (app password). Use repost to create a repost and this tool only to remove one. 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": {
      "repostUri": "<repostUri>"
    },
    "name": "unrepost"
  }
}

Input Schema

Name	Required	Description	Default
`repostUri`	Yes	AT-URI of the repost record to delete (at://did/app.bsky.feed.repost/rkey). Must reference a repost record, not a post.

Output Schema

Name	Required	Description
`success`	Yes	Whether the repost was successfully deleted.
`message`	Yes	Human-readable status message.
`deletedRepost`	Yes	The repost record that was deleted.

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 / repostUri / description

Added value: +"AT-URI of the repost record to delete (at://did/app.bsky.feed.repost/rkey). Must reference a repost record, not a post."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "deletedRepost": {
+      "description": "The repost record that was deleted.",
+      "properties": {
+        "uri": {
+          "description": "AT-URI of the deleted repost record.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "uri"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable status message.",
+      "type": "string"
+    },
+    "success": {
+      "description": "Whether the repost was successfully deleted.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "message",
+    "deletedRepost"
+  ],
+  "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

Behavior5/5

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

Goes beyond annotations by stating the action deletes the record owned by the authenticated user, undoes a previous repost, is irreversible, requires authentication, and is rate-limited. No contradiction with annotations.

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?

Multiple sentences but all are necessary and informative. Front-loaded with purpose, succinctly covers usage, behavior, and constraints 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 output schema exists, no need to explain return values. Tool has single parameter, annotations provide safety hints, and description covers purpose, usage, behavioral effects, and alternatives. Complete for decision-making.

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?

Single parameter 'repostUri' with schema description already providing full meaning. Description does not add extra parameter-level details beyond schema, so baseline score of 3 is appropriate.

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 it 'Remove a repost on AT Protocol' and explains it deletes the repost record. Distinguishes from sibling tool 'repost' by explicitly contrasting creation vs 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 says use 'repost' to create a repost and this tool only to remove one. Also mentions it undoes a plain repost and cannot be undone without re-calling repost, plus authentication requirement.

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