Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Mastodon profile followers

mastodon_profile_followers_list
Read-onlyIdempotent

List the accounts following a Mastodon profile by handle, with cursor-based pagination for retrieving additional pages of followers.

Instructions

List the accounts that follow a Mastodon profile. Requires handle. 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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "mastodon_profile_followers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1 to 80. Default: 40.
cursorNoPass `page.nextCursor` from the previous response to get the next page.
handleYesRequired. Account handle with its home server, e.g. `Gargron@mastodon.social`. A leading `acct:` or `@`, or a profile URL (`https://mastodon.social/@Gargron`, `https://mastodon.social/web/@Gargron`) is also accepted.
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

A3.7/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 without the description. The description adds the pagination behavior (cursor-driven paging) plus the required-parameter constraint, but says nothing about ordering, rate limits, private accounts, or what a returned account record contains.

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?

Three short sentences, front-loaded with the action, then the hard requirement, then the return/pagination note. Nothing extraneous; the only near-redundancy is 'Requires `handle`', which is also marked required in the schema.

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?

There is no output schema, so the description carries the return-shape burden, and it does state that a list is returned plus how to page through it. It is thin on what each follower entry contains (handle vs display name vs id), which is the main remaining gap for a six-parameter list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description edges slightly above it by tying `cursor` to the paginated flow ('use cursor when paginated'), reinforcing how limit/cursor interact across calls. It adds no format detail for `handle` beyond what the schema already spells out with examples.

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?

States a specific verb and resource: 'List the accounts that follow a Mastodon profile.' The use of 'followers' implicitly separates it from mastodon_profile_following_list, but the description never names or contrasts that sibling, so the agent must infer the distinction from the name alone.

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?

Gives one concrete operational rule ('use cursor when paginated') and states the required input, which is useful. It offers no when-to-use vs when-not guidance and does not point to mastodon_profile_following_list or profile_get as alternatives for adjacent goals.

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