Desearch

X Search

x-search

Read-only

Search X (Twitter) using Desearch AI. Optional filters narrow by user, date, language, verification, media, and engagement. Sort stays Top.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	Language code, example: 'en', 'es', 'fr'
`user`	No	User to search for, example: 'elonmusk'
`count`	No	Number of search results to return (default: 20), max is 100
`query`	Yes	Twitter advanced search query, example: 'from:elonmusk since:2023-01-01 min_replies:10'
`end_date`	No	End date in UTC (YYYY-MM-DD). Use with start_date.
`is_image`	No	Include only posts with images.
`is_quote`	No	Include only posts that are quotes.
`is_video`	No	Include only posts with video.
`verified`	No	Filter for verified users.
`min_likes`	No	Minimum number of likes.
`start_date`	No	Start date in UTC (YYYY-MM-DD). Use with end_date.
`min_replies`	No	Minimum number of replies.
`min_retweets`	No	Minimum number of retweets.
`blue_verified`	No	Filter for blue-checkmark verified users.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 20, 2026
- removedInput schema / properties / min_likes / $ref
```
Removed value: -"#/properties/min_retweets"
```
- addedInput schema / properties / min_likes / minimum
```
Added value: +0
```
- addedInput schema / properties / min_likes / type
```
Added value: +"integer"
```
- removedInput schema / properties / min_replies / $ref
```
Removed value: -"#/properties/min_retweets"
```
- addedInput schema / properties / min_replies / minimum
```
Added value: +0
```
- addedInput schema / properties / min_replies / type
```
Added value: +"integer"
```
- removedInput schema / properties / min_retweets / anyOf
```
Removed value: -[
-  {
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "type": "string"
-  }
-]
```
- addedInput schema / properties / min_retweets / minimum
```
Added value: +0
```
- addedInput schema / properties / min_retweets / type
```
Added value: +"integer"
```
First observedOct 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, openWorldHint), so the bar is lower. The description still adds real behavioral context: the Desearch AI backend and the constraint that "Sort stays Top" (sorting cannot be changed), which the agent cannot learn from the schema.

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 action and followed by the filter/sort caveats. Every clause carries information; nothing is redundant.

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 14-parameter search tool with no output schema, the description covers the filter set and the fixed sort behavior, and annotations carry the safety profile. It omits return shape and result ordering details beyond "Top", but nothing essential to invoking it correctly is missing.

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 the baseline is 3. The description maps its filter categories onto the parameters but adds no syntax, defaults, or interaction rules (e.g. start_date/end_date pairing, count max) beyond what the schema already documents.

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?

States a clear verb and resource ("Search X (Twitter)") plus the backend it uses, which is more specific than the bare name. It does not, however, distinguish itself from siblings like `search`, `x-user-posts`, or `x-links-search`, which an agent could plausibly reach for instead.

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?

The description signals that filters are optional and enumerates the filter families (user, date, language, verification, media, engagement), which implies usage. It gives no explicit when-to-use or when-not guidance and names no alternative among the many search siblings.

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

All Desearch 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