TwitterAPI.io MCP Server

Batch Get Tweets by IDs

get_tweets_by_ids

Read-only

Batch-fetch full tweet objects by their numeric tweet IDs. Pass a comma-separated string of up to 50 IDs. Use this when you already have specific tweet IDs (e.g., from a search result, a URL, or a webhook event) and need the full tweet data — author, text, engagement counts, media, etc.

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": {
      "tweet_ids": "<tweet_ids>"
    },
    "name": "get_tweets_by_ids"
  }
}

Input Schema

Name	Required	Description	Default
`tweet_ids`	Yes	Comma-separated tweet IDs (e.g. '1234567890,9876543210'). Batch fetch up to 50 tweets in one call. Tweet IDs are numeric strings.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / tweet_ids / description

Previous value: -"Comma-separated tweet IDs (e.g. '1234567890,9876543210'). Batch fetch up to 100 tweets in one call. Tweet IDs are numeric strings."New value: +"Comma-separated tweet IDs (e.g. '1234567890,9876543210'). Batch fetch up to 50 tweets in one call. Tweet IDs are numeric strings."

First observedSep 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), and with no output schema the description usefully discloses what comes back — author, text, engagement counts, media. It does not cover missing/deleted/suspended tweets or partial-failure behavior in a batch, which is the remaining relevant gap.

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 sentences, both earning their place: the first gives the operation and input shape, the second gives the usage trigger and the return contents. The usage condition is front-loaded with no filler.

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 single-parameter read tool with no output schema, the description supplies the missing piece — the shape of the returned tweet — and the inputs' provenance. Batch semantics for invalid or unavailable IDs are the only materially absent detail.

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 coverage is 100% and the schema already documents the comma-separated format, the 50-tweet cap, and that IDs are numeric strings. The description repeats the same facts without adding format edge cases (e.g. whitespace handling, what happens if some IDs are invalid), so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Batch-fetch full tweet objects by their numeric tweet IDs') plus the scope of the operation. An agent can immediately distinguish it from search_tweets, which finds tweets rather than resolving known IDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly gives the triggering condition — 'when you already have specific tweet IDs' — and even lists where such IDs come from (search result, URL, webhook event). It stops short of naming the sibling alternative (search_tweets) for the case where IDs are not yet known, so it is strong but not fully routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TwitterAPI.io MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?