Skip to main content
Glama

CheapXAPI — Twitter (X) Search, Tweets, Profiles & Followers MCP Server

x_tweet_advanced_search

Advanced search. Search tweets with the X advanced search syntax, e.g. from:NASA since:2026-01-01. Paginated: use cursor / next_cursor.

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": {
      "query": "<query>",
      "queryType": "<queryType>"
    },
    "name": "x_tweet_advanced_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query.
cursorNoPagination cursor. Leave empty for the first page, then pass `next_cursor` from the previous response.
queryTypeYes`Latest` or `Top`.Latest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden. It does disclose that the operation is paginated and that paging continues from `next_cursor`, implicitly confirming a read-only, result-set-returning operation. It says nothing about authentication requirements, rate limits, or result caps, which leaves meaningful gaps for a search endpoint.

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?

Three short sentences, front-loaded with the purpose and then the syntax hint and pagination note. Minor redundancy between "Advanced search." and the following sentence, but nothing extraneous.

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 3-parameter tool with full schema coverage and no output schema, the definition covers purpose, query syntax, and the pagination loop. Only the absence of any guidance on result volume or when to switch to a sibling search tool keeps it below a 5.

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%, so the baseline would be 3. The description exceeds that by demonstrating the operator syntax the `query` field accepts, which the schema only labels as "Search query." It adds nothing about `queryType`, but the syntax example is real added meaning.

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 pairs a specific verb and resource ("Search tweets") with the distinctive mechanism (X advanced search syntax) and gives a concrete operator example. That is enough to tell it apart from simple tweet-list tools, but it never names a sibling such as x_tweet_replies or x_user_tweet_timeline, so the differentiation is inferential rather than explicit.

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?

It shows how to invoke advanced syntax via the example `from:NASA since:2026-01-01`, which is practical orientation for when this tool fits. However, there is no statement of when to prefer it over the many sibling search/timeline tools, and no exclusions or prerequisites are given.

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.

Resources