mastodon-mcp

Boost a status to your followers

boost_status

Idempotent

Boost a status to your followers by providing its ID, with optional account selection. For comments, post a status containing the URL instead.

Instructions

Boost a status to your followers. To add a comment instead, post a status containing its URL. Mastodon has native quote posts from 4.5.0, but this server does not post them.

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>"
    },
    "name": "boost_status"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The status id.
`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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds value by disclosing a server limitation: 'Mastodon has native quote posts from 4.5.0, but this server does not post them.' This gives the agent important context about what the tool will and won't do, 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.

Conciseness5/5

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

The description is three sentences with zero waste. The primary purpose is front-loaded, followed by a clear alternative usage and a relevant server limitation. Every sentence earns its place.

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

Completeness4/5

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

For a tool with 2 parameters, no output schema, and annotations covering safety, the description provides the essential context: what it does, the alternative for commenting, and a server-specific caveat. It does not explicitly mention idempotency or the inverse operation, but these are minor gaps given the annotations and sibling context.

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?

Schema coverage is 100%, so both parameters (id and account) are already fully described in the schema. The tool description adds no additional parameter details, such as format or constraints. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states the tool's purpose: 'Boost a status to your followers.' It uses a specific verb (boost) and resource (status), and differentiates from related actions by noting that commenting requires posting a status with the URL. This distinguishes it from siblings like favourite_status, post_status, and unboost_status.

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 explicitly guides when to use an alternative: 'To add a comment instead, post a status containing its URL.' It also provides server-specific context about quote posts. However, it does not mention the inverse operation (unboost_status) or when to prefer this over other actions, leaving some ambiguity for the agent.

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

Deploy Server