Skip to main content
Glama
Sign In
mastodon-mcp

mastodon-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Hide an account from your timelines without them knowing

mute_account
Idempotent

Hide an account's posts from your timelines without notifying them. Reversible and private, allowing them to still reply to you.

Instructions

Hide an account from your timelines without them knowing. Private and reversible; unlike a block, they can still see and reply to you.

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": "mute_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
acctYes@user@instance, a bare local username, or a numeric id.
accountNoWhich 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.
durationNoSeconds to mute for. 0 or omitted means indefinitely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description adds meaningful context: 'Private and reversible' and the fact that the muted account can still interact. This goes beyond the structured fields and informs the agent about side effects (or lack thereof). It doesn't mention edge cases like repeated muting or effects on notifications, but given the annotations cover safety, this is adequate.

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 sentences, zero waste. The core purpose ('hide an account from your timelines') is front-loaded, followed by a compact, high-value clarification about privacy and the block contrast. Every word 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 simple mutation tool with no output schema and strong annotations, the description covers the essential behavioral contract: what it does, its reversibility, and how it differs from a block. Minor gaps include what happens if the account is already muted or if the duration expires, but those are not critical for correct invocation. The description is sufficiently complete for an agent to decide and call it.

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 description coverage is 100%, so the schema fully documents all three parameters (acct, account, duration) with descriptions. The tool description adds no extra meaning about parameters or their relationships, so the baseline of 3 for high coverage is appropriate.

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?

States a specific verb ('hide'), a resource ('an account'), and the effect ('from your timelines') with the crucial nuance that it's private and reversible. It explicitly contrasts with a block, distinguishing it from sibling tools like block_account, making the purpose unmistakable.

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 contrasts with a block ('unlike a block, they can still see and reply to you'), which clearly implies when to choose mute over block. However, it doesn't explicitly state when not to use it (e.g., 'if you want to prevent them from seeing your posts, use block'), nor does it mention alternatives like unmute. The contrast is strong enough to infer usage, but lacks explicit exclusion.

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

Deploy Server

Other Tools