mastodon-mcp

Unblock an account

unblock_account

Idempotent

Remove a block on a Mastodon account to restore interaction. Note: follows severed by the block don't return; both sides must follow again.

Instructions

Remove a block. Any follows the block severed do not come back; both sides have to follow again.

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": {
      "acct": "<acct>"
    },
    "name": "unblock_account"
  }
}

Input Schema

Name	Required	Description	Default
`acct`	Yes
`account`	No	Which connected account to act as. Matches a full handle (alice@example.social), a bare username (alice), or an instance (example.social). Defaults to the first connected account. Call list_accounts to see them.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-destructive, idempotent behavior. The description adds valuable behavioral context about the lasting effect on severed follows, which is beyond what annotations provide. It does not mention authentication or permission needs, but the key side effect is disclosed.

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 concise sentences, both earning their place: the first gives the core action, the second highlights a crucial side effect. No unnecessary words or restatements.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple mutation tool with annotations, the description covers the core action and a side effect. However, it lacks usage context, does not explain the required parameter, and offers no examples or mention of expected outcomes. It is adequate but leaves some gaps.

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

Parameters2/5

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

Schema coverage is only 50%, with the required 'acct' parameter lacking any description. The description does not clarify what 'acct' should represent, and while the 'account' parameter has schema documentation, the description adds no further meaning. The description fails to compensate for the undocumented required parameter.

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?

Description states the specific verb 'Remove' and resource 'a block', making it clear this unblocks an account. It clearly distinguishes itself from related siblings like block_account, and the added sentence about severed follows provides meaningful context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as block_account or unblock_domain. There is no mention of prerequisites, intended workflow, or conditions under which unblocking should be performed.

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

Deploy Server