Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List tweets from a Twitter list

twitter_list_tweets_list
Read-onlyIdempotent

Fetches recent tweets from members of an X list using its URL or numeric id. Supports cursor-based pagination to retrieve additional results.

Instructions

List recent tweets from members of an X list, by list 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_list_tweets_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. List 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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully supplied. The description adds only that the result is a list and that pagination uses a cursor, which is already implied by the cursor parameter in the schema; ordering, result caps and rate-limit behavior are unstated.

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 tight sentences, front-loading the action and the required parameter. "Requires `url`" is slightly redundant with the schema's required list, but there is no filler and nothing is 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?

For a five-parameter read tool with fully documented schema and annotations and no output schema, the essential calling information is present: what it returns and how to page. Only the absence of result-shape detail (fields per tweet, ordering, max page size) keeps it from a 5.

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 are documented in the schema, including url as "List permalink or numeric id" and cursor as "Opaque pagination cursor returned by a previous response." The description's "by list URL or id" and cursor remark merely restate that, adding no new syntax or format detail.

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 recent tweets from members of an X list") and states the identifiers accepted. It differentiates itself from the similarly named profile/community tweet listers by scoping to list membership, though it does not name 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is operational guidance ("Requires `url`" and "use cursor when paginated") but no when-to-use statement and no explicit routing away from twitter_profile_tweets_list or twitter_community_tweets_list. The agent must infer that this tool is for list-scoped timelines from the name and scope phrase 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