Skip to main content
Glama

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

x_community_search_tweets

Search tweets across communities. Search tweets posted in any community. 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_community_search_tweets"
  }
}

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

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only restates the pagination flow already documented in the cursor schema field. It says nothing about result caps, authentication or access requirements, rate limits, or what the response contains beyond a next_cursor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and the core purpose is front-loaded, but the second sentence duplicates the first almost verbatim and the pagination note repeats the schema. Roughly half the text does not earn its place.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description leaves too much unstated: whether results are limited, how `query` should be formed for community-scoped search, and how this differs from sibling community tweet tools. Only pagination is covered, and that is already in the schema.

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 all three parameters (query, cursor, queryType) are already documented in the schema, and the description adds no syntax or format detail beyond it. The mention of `cursor` / `next_cursor` repeats the schema text rather than extending it, making the baseline 3 appropriate.

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 gives a clear verb+resource ("Search tweets across communities") and specifies the scope (tweets posted in any community), so an agent knows what it retrieves. However, it does not distinguish itself from plausible siblings such as x_community_tweets, which likely also returns community-scoped tweets, and the second sentence merely restates the first.

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 guidance on when to use this tool versus alternatives like x_tweet_advanced_search or x_community_tweets, nor any stated prerequisites or exclusions. The only usage-adjacent content is the pagination instruction, which is invocation mechanics rather than tool selection guidance.

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