Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Twitter community members

twitter_community_members_list
Read-onlyIdempotent

Retrieve the member list of an X community using its URL or numeric ID, with cursor-based pagination for large communities.

Instructions

List members of an X community by community URL or id. Requires url. 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": {
      "url": "<url>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "twitter_community_members_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Community permalink or numeric id.
cursorNoOpaque pagination cursor returned by a previous response.
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 read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds the pagination model (cursor on subsequent calls) and the list-shaped return, but says nothing about member caps, ordering, rate limits, or visibility/privacy constraints.

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 action and scope, then the requirement and pagination hint. Minor redundancy in restating that `url` is required, which the schema already enforces.

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 simple read-only list tool with fully documented parameters and rich annotations, the definition covers what the agent needs to invoke it correctly. No output schema exists, and the description does note the list return shape, though it omits any detail on result size or ordering.

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 five parameters — including `context`, `llm_model`, and `conversation_id` — are already documented in the schema. The description's 'Requires `url`' and 'URL or id' restate schema content rather than adding meaning, so the 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 members of an X community') and clarifies the two accepted address forms (URL or id). It is unambiguous about what is returned, though it does not explicitly distinguish itself from related siblings such as twitter_community_tweets_list or twitter_list_members_list.

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 agent learns it needs a community URL/id and should pass a cursor when the result is paginated. There is no statement of when to prefer this over a sibling community or list tool, nor any exclusion or prerequisite beyond the required `url`.

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