Skip to main content
Glama

web_search

Read-only

Search the web in real time using an AI agent that browses pages, analyzes images, and provides answers with cited sources across multiple reasoning turns.

Instructions

Answer a query using agentic real-time web search.

Grok browses the web across multiple turns, optionally inspecting images on
pages, then synthesizes an answer with citations.

Args:
    prompt: Search query or research question.
    model: Grok model used to drive the agent (default `grok-4.3`).
    allowed_domains: Restrict search to these domains (max 5, mutually exclusive with excluded).
    excluded_domains: Exclude these domains from search (max 5).
    enable_image_understanding: Let the agent analyze images it encounters.
    enable_image_search: Let the agent search for and return image results.
    include_inline_citations: Embed `[1]`-style citation markers into the answer text.
    max_turns: Cap the agent's reasoning/tool turns.
    show_usage: Append a token usage and cost footer to the answer (default False).

Returns:
    Markdown with the answer body followed by a `**Sources:**` list of cited URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNogrok-4.3
promptYes
max_turnsNo
show_usageNo
allowed_domainsNo
excluded_domainsNo
enable_image_searchNo
include_inline_citationsNo
enable_image_understandingNo
Behavior5/5

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

Annotations declare readOnlyHint=true. The description goes beyond by detailing multi-turn agentic browsing, image analysis, return format with citations, and parameter effects. No contradiction with annotations.

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 well-structured with an intro line, parameter list, and return format. It is front-loaded and each line adds value, though slightly verbose but still efficient.

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 9 parameters and no output schema, the description covers purpose, behavior, all parameters, and return format. It omits error handling or rate limits but is sufficient for agent invocation.

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?

Schema description coverage is 0%, so the description fully documents all 9 parameters with clear explanations (e.g., 'Restrict search to these domains (max 5, mutually exclusive with excluded)'). This significantly adds meaning beyond the schema.

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 'Answer a query using agentic real-time web search.' It specifies the verb (answer/query), resource (web), and distinguishes from siblings like x_search by mentioning Grok and agentic browsing.

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 explains the tool's usage for real-time web queries with parameters controlling behavior. However, it does not provide when-not-to-use guidance or compare with alternatives like chat, x_search, or grok_agent, which are present as siblings.

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/merterbak/Grok-MCP'

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