Skip to main content
Glama
Sign In
MCP Web Search Server

MCP Web Search Server

by DmitriyOT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

web_search

Search the web for a query and receive results with titles, URLs, and snippets. Supports multiple search engines and recency filtering.

Instructions

Search the web for a query. Returns a list of results with title, URL, and snippet. Use provider='auto' to try all available search engines.

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": "web_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query
providerNoauto
num_resultsNoNumber of results (1-50)
recency_daysNoLimit results to recent N days

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It discloses output format and provider behavior but lacks information about rate limits, authentication, or what happens on empty results.

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?

Two sentences, front-loaded with purpose, no unnecessary words. Highly concise.

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

Completeness2/5

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

With 4 parameters, no annotations, and no output schema, the description does not fully explain parameters like recency_days or how to choose between siblings. Gaps remain.

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

Parameters2/5

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

Schema coverage is 75%, but description adds only a tip about provider='auto' which is already in schema. Other parameters (num_results, recency_days) are not elaborated beyond schema descriptions.

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?

The description clearly states the tool searches the web and returns results with title, URL, and snippet. However, it does not explicitly differentiate from sibling tools fetch_url and search_and_fetch.

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 gives a tip about using provider='auto' but does not provide when-to-use or when-not-to-use guidance relative to siblings or other contexts.

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