AT Protocol MCP Server

unlike_post

Destructive

Remove your like from a post on the AT Protocol by deleting the associated like record. This action is irreversible and requires authentication.

Instructions

Remove a like from a post on AT Protocol by deleting the like record identified by its AT-URI. This action permanently removes the like and cannot be undone. Requires authentication (app password). Use like_post to add a like. 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": {
      "likeUri": "<likeUri>"
    },
    "name": "unlike_post"
  }
}

Input Schema

Name	Required	Description	Default
`likeUri`	Yes	AT-URI of the like record to delete (at://did/app.bsky.feed.like/rkey); obtained from a previous like_post response or post viewer state.

Output Schema

Name	Required	Description
`success`	Yes	Whether the unlike operation succeeded.
`message`	Yes	Human-readable status message.
`deletedLike`	Yes	The like 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 / likeUri / description

Added value: +"AT-URI of the like record to delete (at://did/app.bsky.feed.like/rkey); obtained from a previous like_post response or post viewer state."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "deletedLike": {
+      "description": "The like record that was deleted.",
+      "properties": {
+        "uri": {
+          "description": "AT-URI of the deleted like record.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "uri"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable status message.",
+      "type": "string"
+    },
+    "success": {
+      "description": "Whether the unlike operation succeeded.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "message",
+    "deletedLike"
+  ],
+  "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.5/5.0

Behavior4/5

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

Annotations already mark the tool as destructive (destructiveHint: true) and non-idempotent (idempotentHint: false). The description adds useful context: 'permanently removes the like and cannot be undone', the authentication requirement, and rate limiting. While valuable, the description largely restates the destructive nature, making the incremental value moderate.

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?

The description is extremely concise, consisting of three short sentences. The first sentence immediately states the core action, followed by a warning about permanence, and then complementary usage info. Every sentence adds value 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 (single parameter, destructive), the description covers all essential aspects: the action, the method (deleting by AT-URI), irreversibility, authentication requirements, alternative tool, and rate limiting. An output schema exists, so the description does not need to detail return values. This is fully complete for its context.

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?

The input schema already provides a detailed description of the 'likeUri' parameter, including its format and source. With 100% schema coverage, the description adds no new parameter-specific information beyond what the schema provides. Therefore, the baseline 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?

The description clearly states the action: 'Remove a like from a post' by deleting a record. It explicitly distinguishes from the sibling tool 'like_post', which is the inverse operation. This provides a specific verb and resource with clear differentiation.

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?

The description provides explicit guidance: it states the tool is for removing a like, mentions the alternative 'like_post' for adding, and specifies prerequisites ('Requires authentication (app password)') and constraints ('Subject to per-tool rate limiting'). This covers when and how to use it effectively.

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