mastodon-mcp

Remove accounts from a list

remove_from_list

Remove accounts from a Mastodon list without unfollowing them. Specify list ID and account handles to update your list membership.

Instructions

Remove accounts from a list. They are not unfollowed.

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": {
      "id": "<id>",
      "accts": "<accts>"
    },
    "name": "remove_from_list"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`accts`	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.7/5.0

Behavior4/5

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

Annotations declare this is a non-readonly, non-destructive, non-idempotent operation. The description adds meaningful behavioral context beyond those annotations by clarifying that removing from a list does not unfollow the account. This prevents a natural misunderstanding, though it does not discuss error cases or effects on previously removed accounts.

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 primary action is stated first, and the key caveat follows immediately. Every word earns its place.

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 two required parameters that are not described in the schema or description, an agent may struggle to invoke it correctly. The high-level purpose is clear, but details about what 'id' refers to and what format 'accts' entries take are missing. With no output schema, the description does not fully compensate for these 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 description coverage is only 33%, with only the optional 'account' parameter described. The two required parameters, 'id' and 'accts', are undocumented in both the schema and the description. The description provides no additional meaning for these parameters, leaving their semantics ambiguous (e.g., what accts entries should contain).

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 states a specific action, removing accounts from a list, and immediately adds a crucial distinguishing detail: 'They are not unfollowed.' This clearly differentiates it from unfollow_account and other list/unlist operations. The verb and resource are explicit and match the title.

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

Usage Guidelines3/5

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

The sentence 'They are not unfollowed' implies a use case and warns against confusing this tool with unfollow actions, but it does not explicitly name alternatives or state when to prefer this tool over add_to_list or unfollow_account. Usage context is implied rather than made explicit.

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

Deploy Server