Skip to main content
Glama

xdataapi: X (Twitter) data

Search

search_tweets
Read-onlyIdempotent

X advanced search. q takes the x.com operators. 1 credit per tweet or profile. product Latest is always available; Top may answer 403 (free).

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": {
      "q": "<q>"
    },
    "name": "search_tweets"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesQuery with x.com operators, e.g. "from:x since:2026-09-01 -filter:replies"
countNoPage size, 1 to 50. Default 20.
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.
cursorNonext_cursor from the previous page
productNoDefault Latest. People returns profiles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / count / description
      Added value: +"Page size, 1 to 50. Default 20."
  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

A4.1/5.0
Behavior4/5

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

Beyond the read-only and open-world annotations, the description discloses a metered cost of one credit per tweet or profile and a possible 403 for Top on free access. These are material billing and availability behaviors, though result and pagination behavior are not further explained.

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?

Four short statements front-load the operation, then cover query syntax, cost, and product availability without filler. The wording is terse, but every clause supplies actionable information.

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?

The fully documented schema covers all five parameters, the annotations establish the safety profile, and the description supplies important cost and availability caveats. With no output schema or explicit sibling-routing guidance, result shape and tool selection remain less complete.

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 coverage is 100%, establishing a baseline of 3. Although the q guidance largely repeats the schema, the description adds new product semantics: Latest is always available, whereas Top may return 403 on free access.

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?

The description identifies the operation and platform as "X advanced search," and the references to tweets and profiles clarify the searchable results. It does not explicitly distinguish this search from the sibling retrieval tools, so it stops short of 5.

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?

The x.com operator support establishes the advanced-query use case, while the Latest/Top availability note provides concrete product-selection guidance. There is no explicit when-not-to-use guidance or named alternative, which keeps this below 5.

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.