Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get multiple tweets

twitter_tweets_batch_get
Read-onlyIdempotent

Batch-retrieve up to 200 tweets by tweet ID or permalink in one request and receive the results as a list.

Instructions

Get up to 200 tweets in one request by ids or permalinks. Requires url. Returns a list.

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_tweets_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Tweet permalink or numeric id. Repeat `url` for each tweet (max 200).
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.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only 'Requires `url`' and 'Returns a list', and says nothing about partial failures, deleted/protected tweets, or ordering of results.

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?

Three short sentences, front-loaded with the capability and limit, then the required parameter and return type. No filler or redundant framing.

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 batch read with full annotation coverage, the description gives enough to call it correctly, and 'Returns a list' compensates for the absent output schema. It is slightly thin on batch-specific edge cases such as what happens when some ids are invalid.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description does add the accepted id/permalink forms and the 200-item ceiling in prose, reinforcing the key parameter. The context/llm_model/conversation_id analytics and pagination-token parameters are left entirely to the schema.

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?

States a specific verb and resource ('Get ... tweets') plus the defining scope of the tool: batching ('up to 200 tweets in one request') and input form ('by ids or permalinks'). That implicitly separates it from twitter_tweet_get, though 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?

Usage is only implied: the 'up to 200 in one request' framing suggests using this when fetching several tweets at once, but there is no explicit when-to-use, when-not, or routing to twitter_tweet_get for a single tweet.

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