Skip to main content
Glama

xdataapi: X (Twitter) data

Tweet

get_tweet
Read-onlyIdempotent

One tweet by numeric id, with its author. 1 credit.

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": {
      "id": "<id>"
    },
    "name": "get_tweet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric tweet id: the digits after /status/ in the tweet URL
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 / id / description
      Added value: +"Numeric tweet id: the digits after /status/ in the tweet URL"
  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
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 the safety profile is covered. The description adds genuinely new operational facts beyond them: the call costs 1 credit and the payload includes the author object, which matters because there is no output schema.

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, front-loaded sentences with zero redundancy: resource scope first, cost second. Nothing could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with full schema coverage and rich annotations, the definition is adequate but thin: it does not mention error behavior for deleted or protected tweets, nor that a cached copy may be returned unless fresh is set.

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 schema already explains that id is the digits after /status/ and details the fresh/cache 2x-credit tradeoff. The description only restates "numeric id" and adds no meaning the schema lacks, so the baseline of 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?

"One tweet by numeric id, with its author" names the resource and the singular scope, which implicitly separates it from batch siblings like get_tweets and search_tweets. It is clear but never explicitly contrasts itself with those alternatives.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says to prefer get_thread for conversation context or get_tweets for multiple ids. The only usage-adjacent signal is the cost line, which is not a selection criterion.

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.