Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List who a Mastodon profile follows

mastodon_profile_following_list
Read-onlyIdempotent

Retrieve the accounts a Mastodon profile follows by providing its handle, with cursor-based pagination to access complete follow lists.

Instructions

List the accounts a Mastodon profile follows. 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_following_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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds useful pagination behavior ('use cursor when paginated') and confirms the return is a list. It does not state result ordering, empty-profile behavior, or rate limits, so it adds modest value beyond the structured fields.

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 with the resource identified first and the prerequisite immediately after, so it is front-loaded and waste-free. The pagination parenthetical is slightly clipped ('when paginated'), which keeps it from a 5.

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?

A simple read tool with rich annotations and full schema coverage needs little prose, and the description covers the essentials. However, it never removes the follows-vs-followers confusion that dominates its sibling set, which is the one omission that matters for an agent choosing a 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 every parameter including limit, cursor, and handle is already documented in the schema; baseline 3 applies. The description only reiterates that `handle` is required and that `cursor` drives pagination, adding no meaning beyond the schema.

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+resource: 'List the accounts a Mastodon profile follows.' An agent can tell this is a following-list read rather than a follower list or profile fetch. It does not explicitly name the confusable sibling `mastodon_profile_followers_list`, so it stops short of a 5.

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?

The only usage statement is 'Requires `handle`', which is a prerequisite rather than when-to-use guidance. There is no mention of when to choose this over `mastodon_profile_followers_list` or `mastodon_profile_get`, which is the primary ambiguity an agent faces here.

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