twitr.sh

x_search

Search X/Twitter tweets with the full operator set — keyword, exact phrase, from-user, language, date range, media type, minimum likes/retweets, verified-only — or search user profiles by keyword. Billed per tweet returned against your resultsLimit cap. Built for tracking what people say about a topic, brand, or ticker in real time.

Guidance: type=search-tweets (default): q required, resultsLimit MANDATORY (billed per tweet returned). Supports the full filter set: fromUser, language, sinceDate/untilDate, mediaType, minFaves, verifiedOnly, exactPhrase, excludeWords, advancedQuery, and more. type=search-users: q required; returns one results page per call — follow report.next_cursor for the next page (each page is a separate paid call).

Input Schema

TableJSON Schema

Name	Required	Description
`q`	Yes	Search query (X operator syntax supported for tweets).
`type`	No	Search tweets (default) or users.
`cursor`	No	search-users: pagination cursor from a previous call's report.next_cursor.
`fromUser`	No
`language`	No
`minFaves`	No
`mediaType`	No
`sinceDate`	No	YYYY-MM-DD
`untilDate`	No	YYYY-MM-DD
`minReplies`	No
`exactPhrase`	No
`minRetweets`	No
`excludeWords`	No
`resultsLimit`	No	search-tweets: MANDATORY max tweets returned, billed per tweet.
`verifiedOnly`	No
`advancedQuery`	No	Raw X search operator string appended to q.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 28, 2026

addedInput schema / allOf

Added value: +[
+  {
+    "else": {
+      "required": [
+        "resultsLimit"
+      ]
+    },
+    "if": {
+      "properties": {
+        "type": {
+          "const": "search-users"
+        }
+      }
+    },
+    "then": {}
+  }
+]

First observedJul 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses billing per tweet, mandatory resultsLimit, and pagination for users. Does not mention any destructive behavior, but search is inherently non-destructive.

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?

Description is well-structured with a guidance section and front-loaded purpose. While it could be slightly more concise, every part adds value and aids understanding.

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?

Given 16 parameters, no output schema, and no annotations, the description provides a comprehensive overview of search functionality, including pagination for users. Lacks details on return format, but overall sufficient.

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 44%, but the description adds meaning for many parameters beyond the schema, such as explaining operator syntax, billing, and pagination. Compensates well for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches X/Twitter tweets or user profiles with a full operator set. It distinguishes from siblings like x_timeline and x_monitor by focusing on search with advanced filtering.

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?

Provides explicit guidance on when to use search-tweets vs search-users, mandatory resultsLimit for tweets, and billing per tweet. However, it does not mention when not to use this tool or list specific alternatives among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All twitr.sh tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

x_search

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources