Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List following ids of a Twitter profile

twitter_profile_following_ids_list
Read-onlyIdempotent

List numeric user IDs of accounts an X profile follows by providing its handle. Use the returned cursor to page through large following lists.

Instructions

List numeric user ids of accounts an X 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": "twitter_profile_following_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 the return shape (a list of numeric ids) and the pagination mechanism, but says nothing about result ordering, whether protected/suspended accounts are included, or rate-limit behavior for an open-world call. Some value beyond annotations, but not rich.

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, no wasted words, and the core action is front-loaded before the requirements and return note. Slightly clipped and note-like rather than structurally organized, but efficient.

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 a fully described 7-parameter schema and no output schema, the description needs only to convey the action and return shape, which it does, including the pagination contract. It omits any mention of the limit ceiling or the latency/cost profile of an open-world fetch, which would help but are not strictly required.

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 the 'by' enum, limit bounds and cursor is already documented in the schema. The description only restates that `handle` is required and that cursor applies to pagination, adding 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?

The description names a specific verb and resource ('List numeric user ids of accounts an X profile follows') and implicitly distinguishes itself from twitter_profile_following_list by stressing 'numeric user ids' rather than full profiles. It never names the sibling explicitly, so the differentiation is left to inference from the word 'ids'.

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?

Usage is only implied: the phrase 'numeric user ids' hints that this is the lightweight path when handles/profiles are not needed, and 'use cursor when paginated' gives a concrete procedural hint. There is no explicit when-to-use/when-not or named alternative, so the agent must reason about siblings on its own.

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