Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List verified followers of a Twitter profile

twitter_profile_followers_verified_list
Read-onlyIdempotent

Lists verified accounts following a specified X profile by handle or numeric user ID, with cursor-based pagination to retrieve larger follower sets.

Instructions

List verified 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_verified_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

B3.2/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, open-world call, so the safety profile is covered. The description usefully adds that results come as a list with cursor-based pagination, but says nothing about result caps, rate limits, or authorization needs beyond a handle.

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 purpose followed by the prerequisite and the return shape. The 'Requires `handle`' clause slightly restates the schema's required list, but nothing is wasted or buried.

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?

With no output schema, the description covers the essentials: what is returned (a list) and how to page (cursor). The mandatory analytics parameters are fully documented in the schema, so their absence from the description is not a gap. Only the absence of any auth or volume limits keeps it from fuller completeness.

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 the `by` enum and the cursor format, are already documented in structure. The description's mention of handle and cursor is consistent but adds no syntax or behavioral meaning beyond the schema, so the baseline of 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 gives a specific verb and resource: verified accounts following an X profile, addressable by handle or numeric id. The 'verified' qualifier is what separates it from the broad followers-list siblings, though it never names those siblings explicitly.

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?

It states the prerequisite that `handle` is required, but gives no guidance on when to choose this verified-only list over the general follower list, nor any note about account type or scope of results. Usage must be inferred from the tool name alone.

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