mastodon-mcp

Stop following an account

unfollow_account

Idempotent

Stop following a Mastodon account by providing its handle. Optionally specify which connected account to act as to manage multiple identities.

Instructions

Stop following 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": "unfollow_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.7/5.0

Behavior2/5

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

Annotations already indicate that this is a mutating, non-destructive, idempotent operation. The description adds nothing beyond the bare fact that the account is unfollowed; it does not disclose edge cases, whether the action is reversible by follow_account, or what happens if the account was not followed in the first place.

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, focused sentence with no filler, making it easy to parse and front-loaded with the essential action. It is concise but borders on tautological since it repeats the title almost verbatim, lacking supporting details that would make the sentence more valuable.

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 an undocumented required parameter and no output schema, the description is too sparse. It does not explain what acct should contain, how the operation interacts with the following list, or whether there are side effects such as removing a follow request or affecting muting/blocking state.

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?

The schema describes the optional 'account' parameter in detail, but the required 'acct' parameter has no description. The tool description only says 'an account,' giving a minimal semantic hint for acct but no information about the expected format (handle, URL, ID), so it does not adequately compensate for the 50% schema description coverage.

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 the action ('Stop following') and the resource ('an account'), and this is distinct from sibling tools like follow_account, mute_account, and block_account. However, it does not explicitly differentiate itself from similar unfollow variants such as unfollow_hashtag, instead relying on the word 'account' to do that work.

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 like mute_account or block_account, nor any exclusion criteria. The only implied usage is that the agent should call it when it wants to unfollow an account, but no context or when-not-to-use information is provided.

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

Deploy Server