x-search-plugin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | No | Optional API key for xAI to use as fallback when no stored OAuth credential is present. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| x_search_statusA | Check x-search-plugin configuration without making a network call. |
| x_searchC | Free-form read-only X/Twitter research using xAI Responses API x_search. |
| search_tweetsB | Search recent X posts by keyword with optional language, dates, and author filter. |
| fetch_tweetB | Fetch and summarize details for one X post URL. |
| get_trendsC | Get current X trends for a region using xAI x_search. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
search_tweets and x_search both perform searches, but their descriptions differentiate: search_tweets is keyword-focused with filters, while x_search is free-form and more general. The other tools are clearly distinct.
search_tweets, fetch_tweet, and get_trends follow a consistent verb_noun pattern, but x_search and x_search_status use an 'x_' prefix that breaks the pattern, mixing styles.
Five tools is well-scoped for a search plugin, covering the most relevant operations without unnecessary bloat.
The tool set covers keyword search, single tweet retrieval, trends, and free-form search, which comprehensively addresses the search domain. Minor gaps exist (e.g., no dedicated user timeline search), but these are workable.