Skip to main content
Glama

web_search

Search the public web by keyword. Returns up to 20 results — each with url, title, description, age, and source — without page bodies. web_scrape returns the full content of a specific result.

It finds current information — recent news, comparison pages, error references, library docs by name. Results are ranked by the upstream search index, not your project.

Example:

{ "project_id": "my-saas", "query": "react server components streaming", "count": 5 }
// Returns: { "query": "...", "results": [{ "url": "...", "title": "...", "description": "...", "age": "2 days ago", "source": "react.dev" }, ...], "count": 5 }
{ "project_id": "my-saas", "query": "react server components", "freshness": "pw", "count": 10 }

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "query": "<query>"
    },
    "name": "web_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of results to return (1-20, default 10).
queryYesSearch text, max 400 chars.
countryNoOptional 2-letter country code to bias results, e.g. "us", "gb", "de".
freshnessNoOptional time filter: pd (past day) | pw (past week) | pm (past month) | py (past year).
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).
safesearchNoOptional content filter: off | moderate | strict (default moderate).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds genuinely new behavior — result cap of 20, field set, omission of page bodies, and that ranking comes from the upstream index rather than the project. It does not cover auth needs or rate limits, but it goes meaningfully beyond the structured hints.

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?

Purpose and the scrape-vs-search distinction are front-loaded in the first two sentences, and the examples are compact. The duplicate example JSON blocks carry some redundancy, but the return-shape sample earns its place given there is no output schema.

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?

With no output schema, the description correctly supplies the result object shape and the 20-result ceiling, and the schema covers all parameter semantics. Missing only operational concerns such as latency, failures, or pagination beyond the count cap, which is minor for a search call.

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

Parameters3/5

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

Schema coverage is 100%, so all six parameters are already documented, including enum-like values for freshness and the project_id resolution behavior. The description's worked examples put `count` and `freshness` in context but add no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Search the public web by keyword") plus the exact return shape (url, title, description, age, source, no page bodies). It explicitly contrasts itself with the sibling `web_scrape`, so an agent can route between them without opening either schema.

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?

Gives clear positive context ("finds current information — recent news, comparison pages, error references, library docs by name") and names `web_scrape` as the alternative when full page content is needed. It stops short of explicit when-not-to-use guidance relative to other search-like siblings, so it is strong but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources