AT Protocol MCP Server

unmute_user

DestructiveIdempotent

Restore a muted user's content by unmuting them without notification. Requires authentication.

Instructions

Unmute a previously muted user to restore their content in your feeds. Reverses an earlier mute_user action without notifying the target. Requires authentication (app password). Use this instead of unblock_user when the account was suppressed via mute rather than block. 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": {
      "actor": "<actor>"
    },
    "name": "unmute_user"
  }
}

Input Schema

Name	Required	Description	Default
`actor`	Yes	Handle (e.g. alice.bsky.social) or DID of the account to unmute.

Output Schema

Name	Required	Description
`success`	Yes	Whether the unmute operation succeeded.
`message`	Yes	Human-readable result message.
`unmutedUser`	Yes	Details of the unmuted account.

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

Added value: +"Handle (e.g. alice.bsky.social) or DID of the account to unmute."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "message": {
+      "description": "Human-readable result message.",
+      "type": "string"
+    },
+    "success": {
+      "description": "Whether the unmute operation succeeded.",
+      "type": "boolean"
+    },
+    "unmutedUser": {
+      "description": "Details of the unmuted account.",
+      "properties": {
+        "actor": {
+          "description": "Handle or DID supplied in the request.",
+          "type": "string"
+        },
+        "did": {
+          "description": "Resolved DID of the unmuted account, if returned by the API.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "actor"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "success",
+    "message",
+    "unmutedUser"
+  ],
+  "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?

Adds context beyond annotations: 'without notifying the target', 'Requires authentication (app password)', 'Subject to per-tool rate limiting.' 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?

Three sentences, each serving a purpose: main action, usage guidance, and behavioral notes. No unnecessary words.

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?

Covers all relevant aspects for a simple unmute operation: purpose, alternative usage, authentication, notification behavior, rate limiting. Output schema exists, so return values are not needed.

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?

Schema coverage is 100% and the schema already describes the 'actor' parameter adequately. The description does not add additional parameter-level details, so baseline 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 'Unmute' and the resource 'a previously muted user' with the outcome 'restore their content in your feeds.' It also distinguishes from the sibling 'unblock_user' by specifying the condition for use.

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 when to use this tool versus alternatives ('Use this instead of unblock_user when the account was suppressed via mute rather than block.') and notes authentication and rate limiting requirements.

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