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.

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": "get_twitter_tweet_advanced_search"
  }
}

Input Schema

Name	Required	Description
`count`	No
`query`	Yes	The query to search for.
`cursor`	No	The cursor to paginate through the results. First page is empty.
`queryType`	Yes	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.

Changed1 schema field changedNov 1, 2026
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "query",
+  "queryType"
+]
```

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.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered; the description adds real behavioral detail beyond that with cursor pagination and the presence of has_next_page/next_cursor in results. It does not discuss auth requirements or rate limits, and the injected pricing boilerplate is noise rather than behavior, so it stops short of 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?

The core is front-loaded: purpose first, then usage alternatives, then query syntax, then pagination. Every sentence about the tool earns its place, but the appended pricing comment block adds unrelated boilerplate that dilutes the signal.

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?

For a six-parameter, cursor-paginated search tool with an output schema present, the description covers the essentials an agent needs: query operator syntax, sort mode, pagination contract, and routing to the correct sibling. Nothing critical to a correct first call is missing.

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?

At 50% schema coverage the description has to carry weight, and it does for the two most important parameters: it enumerates query operators (from:, to:, since:, until:, min_faves:, -filter:replies) and states queryType's default of Latest versus Top. It leaves count, start_time and max_results undocumented in both places, which caps it below 5.

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 and resource ('Search X posts by keyword or query') and immediately scopes it as the primary entry point for content research without tweet IDs or handles. It explicitly names the two sibling tools it is not (get_twitter_user_search, get_twitter_user_tweet_timeline), so an agent can disambiguate 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?

Gives a clear positive condition ('when you do not yet have tweet IDs or handles') plus explicit alternatives for the two adjacent tasks: searching accounts vs reading one account's timeline. Nothing about selection 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?