Skip to main content
Glama

web_search

Read-onlyIdempotent

Search the web to retrieve URLs and metadata snippets without loading full page content. Supports domain-restricted searches via lenses and site filters.

Instructions

Search the web for URLs and metadata without fetching page content. Returns JSON with fields: urls (string array), results (array of {title, url, snippet, displayLink}), query, resultCount. lens and site are mutually exclusive (lens overrides site if both provided). On no matches returns resultCount: 0 with empty results array; on failure returns isError with message. Subject to per-tenant rate limit (default 30 req/min) with automatic provider fallback and circuit breaker recovery. Supports lenses (programming, news, tech, legal, medical, finance, science, government) for domain-restricted search. Use search_and_scrape instead when you need full page content; use news_search for time-sensitive current events; use academic_search for scholarly papers. Results cached 30 min; use time_range to constrain freshness when cache staleness is a concern.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query text (1-500 chars). Be specific with key terms and qualifiers for better results.,required
num_resultsNoNumber of results to return (1-10). Default: 5. Higher values increase latency.
time_rangeNoRestrict to a time period: day, week, month, or year. Omit for all-time results.
safeNoSafeSearch level: off, medium (default), or high.
languageNoFilter by language using ISO 639-1 code (e.g. en, fr, de).
siteNoRestrict to a single domain (e.g. stackoverflow.com). Cannot combine with lens.
exact_termsNoPhrase that must appear verbatim in results.
exclude_termsNoTerms to exclude from results (space-separated).
countryNoRestrict to a country using ISO 3166-1 alpha-2 code (e.g. US, GB).
lensNoApply a curated domain-restricted search lens: programming, news, tech, legal, medical, finance, science, government. Overrides site parameter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
resultCountNo
resultsNo
urlsNo
Behavior5/5

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

Beyond annotations (readOnly, idempotent), the description adds: no-match vs failure behavior, rate limits, provider fallback, circuit breaker, caching duration, and time_range usage. No contradictions 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?

Single paragraph covering all key aspects without redundancy. Could be slightly more structured, but every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters and an output schema, the description covers purpose, alternatives, caching, rate limits, failure modes, and parameter interactions comprehensively.

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?

All 10 parameters have schema descriptions, but the tool description adds valuable interaction context (lens overrides site, num_results latency impact) that aids correct usage.

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 the tool's purpose: searching the web for URLs and metadata without fetching page content. It differentiates from siblings like search_and_scrape and news_search by explicitly naming when to use alternatives.

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

Usage Guidelines5/5

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

Explicitly provides when-to-use guidance: use search_and_scrape for full page content, news_search for current events, academic_search for scholarly papers. Also specifies mutual exclusivity of lens and site parameters.

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/zoharbabin/web-researcher-mcp'

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