Skip to main content
Glama
Sign In

TwittrAPI

by io.github.twittrapi
OverviewDiscussionsAdmin

Get tweets by IDs

tweets_by_ids
Read-onlyIdempotent

Get up to 100 tweets in one call by numeric tweet ID, billed as one call. Results keep the request order; tweets that were deleted or never existed are left out (raw format: an empty {} in their place).

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": {
      "ids": "<ids>"
    },
    "name": "tweets_by_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesNumeric tweet IDs, 1 to 100.
formatNoResponse format (default simple). simple: compact JSON with flat camelCase tweets and users, about 60% fewer tokens. raw: X's full GraphQL JSON, only needed for fields simple leaves out (cards, polls, edit history, community notes).
max_charsNoMaximum characters of JSON to return (default 50000). Longer output is cut with a [TRUNCATED] marker. Lower it to save context, raise it if you need the full response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description instead adds non-obvious behavior: result ordering follows the request, deleted/nonexistent tweets are silently omitted, and in raw format they appear as an empty {}. That placeholder detail is genuinely useful and not inferable from the annotations, though nothing is said about auth or rate limits.

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 front-loaded with the highest-value facts (batch size, billing, ordering, missing-tweet handling). No filler or restatement of the title.

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?

There is no output schema, so the description carries the return-value burden and does address ordering, omissions and the raw-format placeholder. It stops short of sketching the simple-format response shape, but for a straightforward batch lookup this is close to complete.

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 ids, format and max_chars are already well documented and the baseline is 3. The description adds only marginal meaning beyond that — the empty {} behavior clarifies the raw format option — while adding nothing about max_chars or ID validation.

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?

The description gives a specific verb and resource ('Get ... tweets ... by numeric tweet ID') plus the batch scope ('up to 100 tweets in one call'), which distinguishes it from the singular sibling get_tweet and from search_tweets. An agent can tell what it fetches and in what quantity without opening the schema.

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?

The phrase 'billed as one call' implies this is the economical route when fetching many known IDs rather than looping get_tweet, and 'by numeric tweet ID' signals it is not a search tool. However, it never explicitly names get_tweet or search_tweets as the alternatives, nor states the when-not condition (e.g. use search_tweets when you don't already have IDs).

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

All TwittrAPI toolsInspect
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