Skip to main content
Glama

xdataapi: X (Twitter) data

Tweets, batch

get_tweets
Read-onlyIdempotent

Up to 100 tweets by numeric id in one call. 1 credit per tweet found.

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": "get_tweets"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes1 to 100 numeric tweet ids
freshNoRead X again and skip the cache. Costs 2x credits for an item that has a cached copy, the normal price for one that has none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ids / description
      Added value: +"1 to 100 numeric tweet ids"
  2. Changed1 schema field changed
    • changedInput schema / properties / fresh / description
      Previous value: -"Bypass the cache. Costs 2x credits."New value: +"Read X again and skip the cache. Costs 2x credits for an item that has a cached copy, the normal price for one that has none."
  3. First observed

TDQS

A3.5/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 behavior, so the safety profile is covered. The description adds valuable cost context ('1 credit per tweet found', implying unfound ids are not charged) but says nothing about what happens with deleted, protected, or invalid ids, or about result ordering.

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 short, front-loaded sentences with zero filler; the scope and cost model appear first. It is terse to the point of omitting useful behavior, but no sentence is wasted.

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 read-only batch lookup with fully documented parameters and annotations covering safety, the description is largely adequate. The main omissions are return shape (no output schema exists) and handling of ids that cannot be resolved.

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%: the ids array bounds and the fresh cache-bypass semantics (including the 2x credit rule) are fully documented in the schema itself. The description adds no meaning beyond what the schema provides, so the baseline 3 applies.

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 resource (tweets) and scope (up to 100, by numeric id, batched in one call), which implicitly separates it from the single-tweet get_tweet and from search_tweets. It does not name any sibling explicitly, so an agent must infer the distinction from the id-based batching scope.

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 'in one call' signals the batch-efficiency use case, and accepting only numeric ids implies it is not for search. However, there is no explicit when-to-use/when-not guidance and no reference to get_tweet or search_tweets as alternatives, leaving routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.