Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Twitter profile followers

twitter_profile_followers_list
Read-onlyIdempotent

Fetch accounts that follow an X (Twitter) profile by handle or numeric user ID, using cursor pagination to page through follower lists.

Instructions

List accounts following an X profile by handle or numeric user id. 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": "twitter_profile_followers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoTreat the path value as a handle or a numeric user id. Defaults to id when the value is all digits.
cursorNoOpaque pagination cursor returned by a previous response.
handleYesRequired. X (Twitter) profile handle without the leading @, or a numeric user id.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds only a pagination hint (cursor), saying nothing about ordering, result volume caps, rate limits, or whether full account objects or bare identifiers come back — the last being the key behavioral distinction from the ids sibling.

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 scope and with no filler or hedging. "Requires `handle`" is mildly redundant with the schema's required list, which keeps it from a 5.

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?

For a read-only, non-destructive list endpoint whose annotations and full-coverage schema carry the safety and parameter burden, the description is nearly sufficient. The remaining gap is the shape of the returned list, which has no output schema to fall back on and is also what would separate it from the ids-only sibling.

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 all six parameters, including `by`, `cursor`, and the required `context`/`llm_model` bookkeeping fields, are already documented in the schema. The description's "by handle or numeric user id" merely restates the schema's `by` enum and adds no new semantics; 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?

States a specific verb and resource: "List accounts following an X profile", plus the two accepted identifier forms. It does not distinguish itself from closely named siblings such as twitter_profile_followers_ids_list or twitter_profile_followers_verified_list, leaving the agent to infer the difference from names 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?

Offer guidance is limited to "Requires `handle`" and "use cursor when paginated", which is invocation mechanics rather than when-to-use. There is no statement about when to prefer this over the ids or verified-followers variants, so usage is only implied.

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