Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Mastodon server profile directory

mastodon_directory_list
Read-onlyIdempotent

Lists accounts a Mastodon server displays in its directory. Specify the server host to retrieve the list, with cursor support for pagination.

Instructions

List the accounts a Mastodon server shows in its directory. Requires host. Returns a list (use cursor when paginated).

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": {
      "host": "<host>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "mastodon_directory_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesRequired. The Mastodon server to ask, e.g. `mastodon.social`. A server URL is also accepted. The server you name is the one that answers.
limitNoItems per page, 1 to 80. Default: 40.
orderNo`active` (default) most recently active first, `new` newest first.
scopeNo`all` (default) or `local` for the server's own accounts only.
cursorNoPass `page.nextCursor` from the previous response (a plain number is taken as an offset). The list is ordered live, so a row can appear on two pages; remove repeats by `id`, `name` or `url`.
offsetNoItems to skip, as an offset. Prefer `cursor` for the next page. Default: 0.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only that the result is a list and that cursor handles pagination, both of which the schema restates in more detail. It says nothing about which accounts a server exposes in its directory or any result-size caveats.

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?

Two short sentences, front-loaded with the purpose, with no filler. The 'Requires `host`' clause is mildly redundant with the schema's required list and its 'Required.' note, costing a perfect score.

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?

For a nine-parameter read tool with no output schema, the description is thin: it says nothing about the shape of returned accounts, the mandatory analytics parameters (`context`, `llm_model`), or the `conversation_id` sequencing rule, all of which are only in the schema. Annotations and schema carry most of the burden, so it is adequate but incomplete.

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%, including enums for order and scope, cursor semantics, and limit bounds, so the schema does the heavy lifting. The description only repeats the `host` requirement and cursor hint, adding no meaning beyond the schema; baseline 3 applies.

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 description uses a specific verb and resource ('List the accounts a Mastodon server shows in its directory'), which clearly distinguishes it from sibling listing tools such as activity, blocks, or followers. It stops short of explicitly naming a sibling to route against, but 'directory' is a sufficiently distinctive resource.

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 (e.g. activity list, profile followers, search), and no exclusions such as 'local-only servers return few results'. The only advice given is 'use cursor when paginated', which is a pagination hint rather than usage 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