X/Twitter Search (Exa)
Tool
Call the native MCP tool exa-search__web_search_advanced_exa directly with category: "tweet".
Always include category: "tweet".
Critical Filter Restrictions
The tweet category has very limited filter support. These params cause errors:
| Param |
Status |
includeText |
NOT SUPPORTED — 400 error |
excludeText |
NOT SUPPORTED — 400 error |
includeDomains |
NOT SUPPORTED — 400 error |
excludeDomains |
NOT SUPPORTED — 400 error |
moderation |
NOT SUPPORTED — 500 error |
Use the query string itself to filter content — put keywords, hashtags, and exclusions in query.
Supported Parameters
query, numResults, type- Date:
startPublishedDate, endPublishedDate, startCrawlDate, endCrawlDate
- Content:
textMaxCharacters, enableHighlights, enableSummary
additionalQueries — for hashtag variationslivecrawl=preferred — for recent tweets
Call Examples
Tool: exa-search__web_search_advanced_exa
# Recent tweets on a topic
{ query: "Claude Code MCP experience", category: "tweet", startPublishedDate: "2025-01-01",
numResults: 20, type: "auto", livecrawl: "preferred" }
# Product announcements (keywords in query, not includeText)
{ query: "announcing new open source AI tool release", category: "tweet",
startPublishedDate: "2025-12-01", numResults: 15, type: "auto" }
# Developer sentiment
{ query: "developer experience frustrating painful bug", category: "tweet",
numResults: 20, type: "deep", livecrawl: "preferred" }
# Competitor monitoring
{ query: "[INCUMBENT_PRODUCT] review feedback", category: "tweet",
startPublishedDate: "2025-06-01", numResults: 25, type: "auto" }
When to Use
- Social discussions and community sentiment
- Product announcements from company accounts
- Developer opinions and experiences
- Trending topics
- Expert takes and threads
- Competitor/market signal monitoring
Output Format
Return:
- Results — tweet content, author handle, date, engagement if visible
- Sources — tweet URLs
- Notes — sentiment summary, notable accounts, threads vs single tweets
Note: tweet content can be informal, sarcastic, or context-dependent.
1---2name: exa-x-search3description: Search tweets and X/Twitter content using Exa. Finds social discussions, product announcements, developer opinions, trending topics, and community sentiment. Use when searching for tweets, X/Twitter discussions, or social media sentiment.4---56# X/Twitter Search (Exa)78## Tool910Call the native MCP tool `exa-search__web_search_advanced_exa` directly with `category: "tweet"`.1112**Always include `category: "tweet"`.**1314## Critical Filter Restrictions1516The `tweet` category has **very limited** filter support. These params cause errors:1718| Param | Status |19|-------|--------|20| `includeText` | NOT SUPPORTED — 400 error |21| `excludeText` | NOT SUPPORTED — 400 error |22| `includeDomains` | NOT SUPPORTED — 400 error |23| `excludeDomains` | NOT SUPPORTED — 400 error |24| `moderation` | NOT SUPPORTED — 500 error |2526**Use the query string itself to filter content** — put keywords, hashtags, and exclusions in `query`.2728## Supported Parameters2930- `query`, `numResults`, `type`31- Date: `startPublishedDate`, `endPublishedDate`, `startCrawlDate`, `endCrawlDate`32- Content: `textMaxCharacters`, `enableHighlights`, `enableSummary`33- `additionalQueries` — for hashtag variations34- `livecrawl=preferred` — for recent tweets3536## Call Examples3738Tool: `exa-search__web_search_advanced_exa`3940```41# Recent tweets on a topic42{ query: "Claude Code MCP experience", category: "tweet", startPublishedDate: "2025-01-01",43 numResults: 20, type: "auto", livecrawl: "preferred" }4445# Product announcements (keywords in query, not includeText)46{ query: "announcing new open source AI tool release", category: "tweet",47 startPublishedDate: "2025-12-01", numResults: 15, type: "auto" }4849# Developer sentiment50{ query: "developer experience frustrating painful bug", category: "tweet",51 numResults: 20, type: "deep", livecrawl: "preferred" }5253# Competitor monitoring54{ query: "[INCUMBENT_PRODUCT] review feedback", category: "tweet",55 startPublishedDate: "2025-06-01", numResults: 25, type: "auto" }56```5758## When to Use5960- Social discussions and community sentiment61- Product announcements from company accounts62- Developer opinions and experiences63- Trending topics64- Expert takes and threads65- Competitor/market signal monitoring6667## Output Format6869Return:701. Results — tweet content, author handle, date, engagement if visible712. Sources — tweet URLs723. Notes — sentiment summary, notable accounts, threads vs single tweets7374Note: tweet content can be informal, sarcastic, or context-dependent.
CodeAlive-AI