mastodon-mcp

Stop hiding an account

unmute_account

Idempotent

Unmute a Mastodon account to resume seeing its posts in your timeline. Specify the account handle or username to remove the mute.

Instructions

Stop hiding an account.

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": "unmute_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

C2.9/5.0

Behavior3/5

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

Annotations already communicate the key behavioral traits: readOnlyHint is false, idempotentHint is true, and destructiveHint is false. The description adds no additional behavioral context, such as whether unmuting restores notifications or affects existing blocks. It is not contradictory, but it contributes little beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, short sentence with no filler or repetition, making it easy to parse quickly. However, it is so minimal that it largely restates the title without adding useful detail, so it earns high marks for brevity but not maximum utility.

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

Completeness2/5

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

For a tool with one required parameter and no output schema, the description should at least explain what the required 'acct' should contain and what happens after unmuting. It does neither, leaving the agent without enough information to call the tool correctly on its own.

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 description coverage is 50%, and only the optional 'account' parameter is explained. The required 'acct' parameter is entirely undocumented, and the description does not clarify whether it is a username, account ID, or handle, nor how it relates to 'account'. The description fails to compensate for this gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action ('Stop hiding an account') with a recognizable verb and resource. However, it is nearly identical to the title and does not distinguish this from related sibling tools like unmute_conversation or unblock_account, leaving the differentiation to the reader.

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?

There is no guidance about when to use this tool versus alternatives such as mute_account, unmute_conversation, or unblock_account. The description states only what the tool does, not when it should be chosen or what conditions make it appropriate.

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

Deploy Server