mastodon-mcp

Unblock an instance

unblock_domain

Idempotent

Lift a domain block to restore interaction with that domain. Followers removed by the block are not restored.

Instructions

Lift a domain block. Followers removed by the block are not restored.

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": {
      "domain": "<domain>"
    },
    "name": "unblock_domain"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	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

A4.3/5.0

Behavior4/5

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

The description adds a meaningful behavioral consequence beyond annotations: 'Followers removed by the block are not restored.' Since annotations already convey non-read-only and idempotent behavior, this additional side effect is valuable and sufficient for this low-complexity operation.

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 sentences with no filler: the first states the primary action, the second states the most important side effect. Every word earns its place.

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 only two parameters, no output schema, and annotations that already cover mutation and idempotence, the description is complete. It tells the agent what happens and the key non-obvious consequence, leaving no critical call-time information missing.

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 account parameter is well documented in the schema. The required domain parameter has no schema description, but the description's 'Lift a domain block' and the title 'Unblock an instance' make its meaning clear. Still, the description does not add explicit parameter-level details about what format `domain` should take, so it is adequate but not exceptional.

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 uses a specific verb ('Lift') and resource ('domain block'), making the action unambiguous. The title and sibling tool block_domain reinforce that this is the inverse operation, so there is no confusion with account-level tools.

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

Usage Guidelines4/5

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

The description clearly states when to use the tool: when a domain block should be removed. It does not explicitly name block_domain as the alternative or provide when-not-to-use conditions, but the context is clear enough for an agent to route correctly.

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

Deploy Server