Skip to main content
Glama
Sign In
mastodon-mcp

mastodon-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List instances you have blocked

get_blocked_domains
Read-onlyIdempotent

Fetch blocked instances from your Mastodon account. Use optional limit and pagination to navigate the list.

Instructions

Whole instances you have blocked.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_blocked_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many. Pages automatically. Default 40.
max_idNoContinue from a previous page.
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

C2.9/5.0
Behavior2/5

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

The annotations already communicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds no behavioral context beyond that: no mention of pagination behavior, sorting, rate limits, or what exactly is returned. It merely restates the subject matter.

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 extremely short with no wasted words and the core scope is front-loaded. It is a fragment rather than a complete sentence, but given the tool's simplicity, the brevity is mostly appropriate.

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

Completeness3/5

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

The schema and annotations cover parameters and safety, and the title conveys the operation. However, there is no output schema and the description does not explain what the return value looks like (e.g., a list of domain strings) or how pagination works beyond the max_id hint, leaving minor ambiguity for a listing tool.

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 limit, max_id, and account are already fully documented with clear meanings. The description contributes no additional parameter-level nuance, so it sits at the baseline for tools with complete schema 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 title provides a clear verb+resource: 'List instances you have blocked.' The description reinforces the scope with 'Whole instances,' which distinguishes this from per-account or per-user block tools like get_blocks. However, the description itself is a fragment without an explicit verb and does not name any sibling tool.

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 on when to use this tool versus alternatives such as get_blocks, block_domain, or unblock_domain. The description gives no context about typical use cases, prerequisites, or exclusions, leaving the agent to infer entirely from the name and schema.

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