Skip to main content
Glama
serper-search-mcp-server

serper-search-mcp-server

search_many

Run multiple web searches in parallel and deduplicate URLs across queries to compare topics, gather multi-angle context, or fan out sub-queries.

Instructions

Run multiple web searches in one call (parallel). Duplicate URLs across queries are removed automatically. Great for comparing topics, gathering multi-angle context, or fanning out sub-queries. Each query costs 1 credit.

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": {
      "queries": "<queries>"
    },
    "name": "search_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoISO 3166-1 alpha-2 country code (e.g. "US", "GB"). Default: "US".
queriesYesSearch queries (1–10 items, each max 400 chars / 50 words).
ui_langNoUI language (e.g. "en-US"). Default: "en".
freshnessNoTime filter: pd=past day pw=week pm=month py=year any=none (historical). Pass pd/pw/pm/py whenever the user asks for latest/current/recent results ("today", "this week", "latest", current year); omit or "any" for timeless or historical questions. The response footer echoes the filter that was applied.
safesearchNo"off" | "moderate" | "strict". Default: "moderate".moderate
num_resultsNoResults (1–20, default 5). Note: >10 results uses 2 Serper credits.
search_langNoLanguage code (e.g. "en", "de"). Default: "en".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.1.0
    • changedInput schema / properties / freshness / description
      Previous value: -"Time filter: pd=day pw=week pm=month py=year."New value: +"Time filter: pd=past day pw=week pm=month py=year any=none (historical). Pass pd/pw/pm/py whenever the user asks for latest/current/recent results (\"today\", \"this week\", \"latest\", current year); omit or \"any\" for timeless or historical questions. The response footer echoes the filter that was applied."
    • changedInput schema / properties / freshness / enum
      Previous value: -[
      -  "pd",
      -  "pw",
      -  "pm",
      -  "py"
      -]New value: +[
      +  "pd",
      +  "pw",
      +  "pm",
      +  "py",
      +  "any"
      +]
  2. First observedv4.0.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: parallel execution, automatic cross-query URL deduplication, and per-query credit cost. It does not cover what happens if one query fails, whether results are grouped per query, or any rate-limit behavior, which keeps it short of a 5.

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?

Four short sentences, capability first, then dedup behavior, then use cases, then cost. No filler, no repetition, and the most decision-relevant facts are front-loaded.

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?

For a 7-parameter, single-required-input tool with full schema documentation and no output schema, the description covers the non-obvious traits an agent needs: batching, dedup, and credit cost. Return shape and partial-failure semantics are the only meaningful gaps.

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%, including enum semantics for freshness and safesearch and the credit caveat for num_results > 10, so baseline is 3. The description adds no parameter-level meaning beyond noting that "each query costs 1 credit," which is only a partial restatement of what the schema already documents.

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 ("Run multiple web searches") plus a scope qualifier ("in one call (parallel)") that immediately separates it from the single-query siblings like search/search_web. An agent can pick this tool without inspecting any 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 concrete usage contexts: comparing topics, gathering multi-angle context, fanning out sub-queries. It never states the negative case explicitly (e.g. "use search instead if you only have one query"), so routing back to the single-query sibling is left implicit rather than spelled out.

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