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

serper-search-mcp-server

search_shopping

Search Google Shopping by query and return product prices, ratings, and delivery info to compare buying options.

Instructions

Google Shopping search via Serper API. Returns products with prices, ratings, and delivery info.

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_shopping"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesProduct or shopping query.
countryNoISO 3166-1 alpha-2 country code (e.g. "US", "GB"). Default: "US".
ui_langNoUI language (e.g. "en-US"). Default: "en".
num_resultsNoResults (1–20, default 10). Note: >10 results uses 2 Serper credits.
search_langNoLanguage code (e.g. "en", "de"). Default: "en".
link_resolutionNoGoogle result links beyond the top 3 may come back as google.com/goto redirects. "auto" (default): top 3 resolved, any leftover goto links get a search_id for resolve_links. "all": also resolve every link now (free, but adds ~30 s when goto links are present). "none": fastest, links exactly as Google returns them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does disclose the return payload (prices, ratings, delivery info), which is genuine behavioral context. It omits other meaningful traits such as credit cost, result caps, and the link-resolution/redirect behavior that the schema introduces, so it is only partially transparent.

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 short sentences: the first identifies the tool and source, the second front-loads what comes back. No filler or repetition.

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?

Six parameters are fully documented in the schema and there is no output schema, so the description's one-line summary of return values is sufficient for correct invocation. A brief note on credit consumption or the redirect caveat would make it fully self-contained.

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%, so every parameter including the link_resolution enum and its 30-second trade-off is already documented in structured data. The description adds no parameter meaning beyond that, making the baseline 3 correct.

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 names a specific verb and resource ("Google Shopping search via Serper API") and states the returned data (products with prices, ratings, delivery info), which is enough to distinguish it from search_web, search_images, or scrape. It stops short of explicitly contrasting itself with any sibling, so it lands at 4 rather than 5.

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 word "Shopping" — an agent can infer this is the tool for product/price queries. There is no explicit statement of when to prefer it over search_web or search, and no exclusions or prerequisites.

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