Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List accounts that retweeted a tweet

twitter_tweet_retweets_list
Read-onlyIdempotent

Retrieve the accounts that retweeted a specific tweet by permalink or numeric ID, with cursor-based pagination for complete result lists.

Instructions

List accounts that retweeted a tweet, by permalink 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_tweet_retweets_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Tweet 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.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description's burden is lower. It adds the pagination mechanic and the required input, but does not cover ordering, rate limits, or what each account entry contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero redundancy, with the resource and required input front-loaded before the pagination note. Every clause carries information an agent can act on.

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?

Given full schema coverage and annotations covering the safety profile, the definition is nearly complete for a simple read tool. The one soft gap is that it does not characterize the returned account objects, which matters slightly since there is no output schema.

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 the schema fully documents all five parameters including cursor and context. The description's mention of permalink-or-id and cursor adds only marginal meaning beyond the schema's own wording, making 3 the appropriate baseline.

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 accounts that retweeted a tweet — with the accepted identifier forms (permalink or numeric id). It is distinct from quote/reply listing siblings by resource, though it never explicitly contrasts them.

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 hard prerequisite (requires `url`) and gives a pagination cue ('use cursor when paginated'), but gives no explicit when-to-use guidance or routing against alternatives such as twitter_tweet_quotes_list or twitter_tweet_replies_list.

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