Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Mastodon profile collections

mastodon_profile_collections_list
Read-onlyIdempotent

Lists a Mastodon account's curated collections and their member accounts so you can inspect how a profile groups related accounts.

Instructions

List an account's curated collections of accounts (Mastodon 4.7 and later), with the member accounts. Requires handle. Returns a list.

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_collections_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.4/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. The description adds one genuine behavioral fact beyond that – the Mastodon 4.7+ server requirement – but does not say how pre-4.7 servers respond (error vs. empty list) or whether the result is paginated. Useful but thin on top of structured data.

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?

Three short sentences, front-loaded with what is returned, then the requirement, then the return shape. Nearly zero waste, though 'Returns a list' is low-information for a tool whose name already ends in _list; the version qualifier is well-placed inside the first sentence rather than buried.

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?

With no output schema, the description's 'Returns a list' is the only return-value signal, and it says nothing about item shape (collection name, member list nesting) or pagination limits. Annotations cover the read-only profile, so the remaining gap is modest but real for a list tool whose payload is a nested collection-with-members structure.

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%, and the handle parameter's format variants (acct:, @, profile URL) are fully documented in the schema. The description's 'Requires `handle`' merely restates the schema's required field and adds no new meaning. Baseline 3 applies since the schema carries the semantics.

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 an account's curated collections of accounts') and adds scope detail that separates it from scalar list siblings: it returns collections plus their member accounts. The Mastodon 4.7+ qualifier further narrows what this tool is. It doesn't explicitly name an alternative, but the resource is distinctive enough (collections, not followers/following/posts) that an agent can route correctly.

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?

'Requires `handle`' and the '4.7 and later' version note give a prerequisite and a compatibility condition, which is real usage guidance. However, there is no explicit when-to-use vs. alternatives (e.g., followers_list or following_list) and no statement about what happens on servers older than 4.7. Usage is implied rather than prescribed.

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