Skip to main content
Glama

XCROP X (Twitter) data

Search posts

search_tweets
Read-only

Search X posts. Supports X search operators in the query (from:, to:, lang:, min_faves:, since:, until:, -filter:replies). Costs 15 credits per post returned.

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

Input Schema

NameRequiredDescriptionDefault
sortNolatest first, most engaged first, or posts with media (values of POST /v2/search)latest
countNoHow many posts to return (default 10, max 100)
queryYesSearch query, X operators allowed
cursorNonext_cursor from the previous page, to continue

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds the important cost model ('15 credits per post returned'), which is behavioral context an agent cannot get from structured fields. It stops short of describing pagination behavior or result ordering, but the credit disclosure is a real value-add.

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 sentences, front-loaded with the core purpose and immediately followed by the two facts that matter most (operator support and cost). No filler or redundancy.

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 four-parameter read-only search tool with a fully described schema and no output schema, the description covers purpose, query syntax, and cost. Only minor items such as pagination expectations or result ordering are left implicit.

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%, so all four parameters are already documented, establishing a baseline of 3. The enumerated operator list (from:, to:, lang:, min_faves:, since:, until:, -filter:replies) adds concrete syntax meaning for the query parameter beyond the schema's vague 'X operators allowed'.

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 states a specific verb and resource ('Search X posts') and scopes it to keyword/operator queries, which separates it from timeline-style siblings like get_user_tweets. It does not name any sibling explicitly, so differentiation is inferable rather than stated.

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?

Usage is implied by 'Search X posts' plus the supported operator list, which tells an agent this is the right tool for filtered/keyword lookups. There is no explicit when-to-use vs. when-not-to-use guidance or pointer to alternatives such as search_users or get_user_tweets.

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