AIsa X / Twitter

Advanced Search

get_twitter_tweet_advanced_search

Read-onlyIdempotent

Search X posts by keyword or query with X's advanced search operators, sorted by Latest (default) or Top. This is the primary entry point for X content research when you do not yet have tweet IDs or handles. Supports operators in the query string such as from:, to:, since:, until:, min_faves:, and -filter:replies. Cursor-paginated; returns tweets with has_next_page and next_cursor. To search accounts rather than posts use get_twitter_user_search. To read one account's own posts use get_twitter_user_tweet_timeline.

Usage-based billing; Default request estimate: $0.003 USD (not a fixed price). Account-specific pricing and final settlement may differ.

Input Schema

Name	Required	Description
`count`	No
`query`	No	The query to search for.
`cursor`	No	The cursor to paginate through the results. First page is empty.
`queryType`	No	The query type to search for. Provider reference (supplier schema): `{"default":"Latest","enum":["Latest","Top"],"type":"string"}`.
`start_time`	No
`max_results`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

addedInput schema / properties / cursor / description

Added value: +"The cursor to paginate through the results. First page is empty."

addedInput schema / properties / query / description
```
Added value: +"The query to search for."
```

addedInput schema / properties / queryType / description

Added value: +"The query type to search for.\n\nProvider reference (supplier schema): `{\"default\":\"Latest\",\"enum\":[\"Latest\",\"Top\"],\"type\":\"string\"}`."

Changed9 schema fields changedOct 15, 2026
- addedInput schema / properties / count
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / cursor / description
```
Removed value: -"The cursor to paginate through the results. First page is empty."
```
- addedInput schema / properties / max_results
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / query / description
```
Removed value: -"The query to search for."
```
- removedInput schema / properties / queryType / default
```
Removed value: -"Latest"
```
- removedInput schema / properties / queryType / description
```
Removed value: -"The query type to search for."
```
- removedInput schema / properties / queryType / enum
```
Removed value: -[
-  "Latest",
-  "Top"
-]
```
- addedInput schema / properties / start_time
```
Added value: +{
+  "type": "string"
+}
```
- changedInput schema / required
```
Previous value: -[
-  "query",
-  "queryType"
-]New value: +[]
```
First observedSep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the lower bar applies. The description still adds real behavior: cursor pagination semantics, the has_next_page/next_cursor return fields, sort modes, and supported query operators. It omits auth requirements and rate limits, which keeps it from a 5.

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?

Front-loaded with purpose, then operators, pagination, and alternatives in a tight sequence where each sentence carries information. The injected pricing boilerplate is not authored content but does add noise.

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

Completeness5/5

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

An output schema exists so return values need not be exhaustively explained, and annotations carry the safety profile. The description still covers usage context, alternatives, pagination flow, and query syntax, so nothing an agent needs to invoke 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 coverage is 50%, so the schema does part of the work. The description usefully explains the query-string operator syntax and the Latest/Top sort (mapping to queryType), but count, max_results, and start_time are undocumented in both places. It adds value over the schema without fully compensating for the coverage gap.

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?

States a specific verb (search) and resource (X posts) and immediately differentiates itself by naming the two sibling alternatives for account search and user timelines. An agent can distinguish this from any account-scoped tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly declares when to use it ('primary entry point for X content research when you do not yet have tweet IDs or handles') and routes to the correct alternatives ('to search accounts use get_twitter_user_search', 'to read one account's posts use get_twitter_user_tweet_timeline'). Nothing is left to inference.

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

All AIsa X / Twitter 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.

Resources

Need Help?