Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List follower ids of a Twitter profile

twitter_profile_followers_ids_list
Read-onlyIdempotent

Retrieve numeric user IDs of accounts following an X (Twitter) profile by handle, with cursor-based pagination to page through large follower lists.

Instructions

List numeric user ids of accounts following an X 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": "twitter_profile_followers_ids_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.
limitNoRequested page size (1–5000).
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 readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds only the pagination hint and handle requirement, without disclosing rate limits, whether cursors expire, or what an empty result means.

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 with the purpose front-loaded and no wasted wording. "Returns a list" is mildly redundant but useful since there is no output 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?

With no output schema, the description usefully states the return shape (a list of numeric ids) and the pagination mechanism. Combined with a fully documented schema and rich annotations, this is largely complete, though it omits guidance on iterating cursors to exhaustion.

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 parameters like limit, cursor, by, and handle are fully documented in the schema itself. The description merely restates the handle requirement and cursor usage, adding no syntax or semantics beyond what the schema provides.

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 states a specific verb and resource: "List numeric user ids of accounts following an X profile." The emphasis on "numeric user ids" implicitly distinguishes it from the sibling twitter_profile_followers_list, which returns full profiles, but no sibling is named explicitly.

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?

It states the `handle` prerequisite and hints "use cursor when paginated," which informs invocation. However, it never says when to choose this tool over twitter_profile_followers_list or the verified-only variant, leaving the agent to infer the distinction from the word "ids."

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