Skip to main content
Glama

x_search

Read-only

Search X posts and profiles by keyword, handles, and date range.

Instructions

Query X posts and profiles using xAI's real-time X search tool.

Args: prompt: The search question or instruction. allowed_x_handles: Restrict search to posts from these X handles. from_date: Earliest post date, ISO format (e.g. "2026-06-01"). to_date: Latest post date, ISO format (e.g. "2026-07-01").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYes
to_dateNo
from_dateNo
allowed_x_handlesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoStructured payload for web_search / x_search / code_execution.
textNoHuman-formatted output (includes footers, citations, cost summary).
modelYesActual executing model ID (e.g. 'grok-4.5').
planeNoAPI
routeYesHigh-level route (fast/agentic/research/etc.).
tokensNoTotal tokens consumed.
profileNoInternal routing profile.
cost_usdNoExact USD cost from xAI billing metadata.
responseYesRaw model output or primary content.
citationsNoNative xAI/X citations with URL + snippet.
latency_secNo
finish_reasonNounknown
reasoning_effortNoGrok 4.5+ native reasoning level.
Behavior3/5

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

The annotations already provide readOnlyHint=true, indicating it is a safe read operation. The description adds no additional behavioral context beyond that (e.g., rate limits, authentication needs), so the value is limited.

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 description is concise and well-structured, with a single purpose sentence followed by a clear parameter list. It is efficient but could be slightly more compact.

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?

Given the presence of an output schema, the description adequately covers input semantics and the tool's purpose. It lacks details about result format or limitations, but the output schema likely fills that gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains each parameter with practical examples (e.g., ISO date formats, restricting handles), fully compensating for the 0% schema description coverage. Agents can understand how to use each field correctly.

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?

The description clearly states it queries 'X posts and profiles' using 'real-time X search', which is a specific verb and resource. This distinguishes it from sibling tools like web_search or search_knowledge.

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 does not provide explicit guidance on when to use this tool vs alternatives. While the context of sibling tools implies it is for X-specific searches, no 'when not to use' or comparison is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/djtelicloud/grok-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server