Skip to main content
Glama
NakanoSanku

grok-web-search-mcp

by NakanoSanku

web_search

Search the web and X (Twitter) using natural language. Get answers with citations, optional image understanding, and domain or date filters.

Instructions

Live web and X search via Grok. Returns ok, text (answer), citations (URL list). Optional images: public URL, data:image/...;base64,..., or local file path (max 5) to ask about a picture while searching. Supports web domain filters, X handle/date filters, and reasoning_effort (low/medium/high). Image understanding applies to browsed pages and X posts; video understanding applies to X posts only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoOptional model override (default from GROK_MODEL / grok-4.5).
queryYesNatural-language search question or topic.
imagesNoOptional image input(s) for visual questions: URL / data-URI / local path (comma or newline separated, max 5). Not an image-search API.
to_dateNoOptional inclusive X search end date (YYYY-MM-DD).
from_dateNoOptional inclusive X search start date (YYYY-MM-DD).
image_detailNoVision detail for input images: low | high | auto (default high).
system_promptNoOptional system instruction prepended to the request.
allowed_domainsNoOptional comma-separated allowlist (max 5). Mutually exclusive with excluded_domains.
excluded_domainsNoOptional comma-separated denylist (max 5).
reasoning_effortNoOptional thinking length for reasoning models: low | medium | high.
allowed_x_handlesNoOptional comma-separated X handle allowlist (max 20). Mutually exclusive with excluded_x_handles.
excluded_x_handlesNoOptional comma-separated X handle denylist (max 20).
enable_image_understandingNoAnalyze images found on browsed pages and X posts (default on).
enable_video_understandingNoAnalyze videos found in X posts (default off).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries full burden. It discloses return format, image handling constraints (max 5, types), and scoping of image/video understanding. It lacks explicit mention of read-only nature but is otherwise transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (6 sentences), front-loaded with core purpose, and every sentence adds meaningful information without redundancy.

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 tool's complexity (14 parameters, optional features) and the presence of an output schema, the description covers most behavioral aspects. Minor gaps exist (e.g., rate limits, indexing scope), but overall it is thorough.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by summarizing key parameters (domain filters, reasoning_effort) and clarifying behavior of image/video understanding fields, which are not detailed in schema descriptions.

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 performs 'Live web and X search via Grok' and details return values. It uses a specific verb (search) and resource (web and X), and the purpose is unambiguous.

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

Usage Guidelines4/5

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

While no sibling tools exist for comparison, the description provides clear context on features and filters, sufficiently guiding usage. It could benefit from explicit when-not-to-use, but the absence of alternatives makes this less critical.

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/NakanoSanku/grok-web-search-mcp'

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