Skip to main content
Glama

Web Search

search
Read-only

Query the web for results via Brave, SearXNG, or DuckDuckGo, filtered by domain and freshness with page-based pagination.

Instructions

Search the web and return results. Uses Brave Search API if BRAVE_API_KEY is set, otherwise falls back to SearXNG and then DuckDuckGo. Supports domain filtering (site), freshness, and pagination (page).

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page for pagination (default 1; ignored by the DuckDuckGo fallback)
siteNoRestrict results to a domain, e.g. "github.com"
countNoNumber of results (1-20, default 5)
queryYesSearch query
freshnessNoOnly return results from the last day/week/month/year (ignored by the DuckDuckGo fallback)
timeoutMsNoOverall retrieval deadline in milliseconds, including downloads (default 25000)

Output Schema

NameRequiredDescriptionDefault
sourceYes
timingYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv6.0.0
    • addedInput schema / properties / freshness
      Added value: +{
      +  "description": "Only return results from the last day/week/month/year (ignored by the DuckDuckGo fallback)",
      +  "enum": [
      +    "day",
      +    "week",
      +    "month",
      +    "year"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "1-based results page for pagination (default 1; ignored by the DuckDuckGo fallback)",
      +  "maximum": 10,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Restrict results to a domain, e.g. \"github.com\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / timeoutMs
      Added value: +{
      +  "description": "Overall retrieval deadline in milliseconds, including downloads (default 25000)",
      +  "maximum": 120000,
      +  "minimum": 500,
      +  "type": "integer"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "results": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "snippet": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "title",
      +          "url",
      +          "snippet"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "timing": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "results",
      +    "source",
      +    "timing"
      +  ],
      +  "type": "object"
      +}
  2. Addedv1.0.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive, non-idempotent), so the description's added value is the provider chain — Brave first, then SearXNG, then DuckDuckGo — which tells the agent results and capabilities can vary by deployment. It stops short of saying results are non-deterministic across retries, which matters given idempotentHint=false.

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?

Three short sentences, purpose front-loaded, then environment-dependent behavior, then capabilities. No filler, though the feature list marginally repeats the schema's parameter names rather than adding information.

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 an output schema present, return-shape explanation is unnecessary, and annotations plus schema cover safety and parameter constraints. The description completes the picture with the backend fallback chain, which is the one behavior an agent could not learn from structured fields.

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 description coverage is 100% and every parameter carries its own description with ranges, defaults, and the DuckDuckGo caveats, so the schema does the heavy lifting. The description names site, freshness, and page but adds no semantics beyond what the schema already states, and ignores count and timeoutMs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Search the web and return results" gives a specific verb and resource that an agent can act on immediately, and the provider-fallback sentence adds useful scope. It does not distinguish itself from siblings like fetch, extract, or research, so an agent must still infer that this is for discovery rather than retrieving known URLs.

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?

Usage is only implied by the verb "search"; there is no explicit statement of when to prefer this over fetch, extract, fetch_batch, or research. The fallback chain hints at reliability trade-offs, but the agent gets no routing guidance.

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

Deploy Server

Other Tools