Skip to main content
Glama
Sign In
mastodon-mcp

mastodon-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Stop being notified about replies to this thread, without leaving it

mute_conversation
Idempotent

Mute a conversation to stop reply notifications without leaving the thread. Reduce alert noise when a post gets many responses.

Instructions

Stop being notified about replies to this thread, without leaving it. The tool nobody reaches for until a post goes unexpectedly wide.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe status 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that the tool is a non-read-only, idempotent, non-destructive operation. The description adds behavioral context beyond the annotations by stating that muting does not require leaving the thread, which clarifies the key side effect an agent needs to know.

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 first sentence is a tight, front-loaded description of the tool's purpose. The second sentence is a stylistic aside that does not add operational value, so it is not flawless, but overall the description is still appropriately short.

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 two-parameter, idempotent mutation with no output schema, the description plus annotations cover what the tool does and its main side effect. It could explicitly point to unmute_conversation as the reversal, but nothing essential for invoking the tool correctly is missing.

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%, with both id and account already documented including how account matching works and the default. The description adds no additional parameter-level meaning, so it correctly sits at the schema-covered baseline of 3.

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 first sentence states a specific action and resource: stop being notified about replies to this thread without leaving it. This clearly scopes the tool to conversation-level muting and distinguishes it from account-level mute tools and the sibling unmute_conversation. The added flavor sentence does not obscure the purpose.

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 description implies a use case with 'until a post goes unexpectedly wide' but provides no explicit guidance about when to choose this over alternatives like mute_account or how to reverse it with unmute_conversation. This is only implied usage context, not actionable when/when-not guidance.

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