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

serper-search-mcp-server

search_places

Find local businesses and places via Google Maps/Places search, returning addresses, phone numbers, weekly hours, ratings, and GPS directions links. Filter by rating, sort by reviews, and control result density.

Instructions

Google Places / Maps search via Serper API. Returns local businesses with address, phone, full 7-day hours, ratings, GPS + Directions links. Rich by default; verbosity=compact keeps only title/rating/address.

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

Input Schema

NameRequiredDescriptionDefault
queryYesPlace or business query (e.g. "coffee shops in Tokyo").
countryNoISO 3166-1 alpha-2 country code (e.g. "US", "GB"). Default: "US".
sort_byNoSort results.
ui_langNoUI language (e.g. "en-US"). Default: "en".
providerNoSearch backend: auto (failover chain), serper, tavily, brave, exa, firecrawl. Default: auto.auto
max_charsNoTruncate response to this many characters (0 = no limit).
verbosityNoOutput density: auto (server picks per audience), compact (~800 tokens, dev fast path), standard (KG+Box+10), full (everything, always for places/shopping/images/scholar). Default: auto.auto
min_ratingNoMinimum rating filter (e.g. 4.5).
num_resultsNoResults (1–20, default 5). Note: >10 results uses 2 Serper credits.
search_langNoLanguage code (e.g. "en", "de"). Default: "en".
snippets_onlyNoReturn 1-line snippets only (token-saving for agents). Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.1.0
    • removedInput schema / properties / open_now_only
      Removed value: -{
      -  "default": false,
      -  "description": "Filter to currently-open places (client-side via hours text). Default: false.",
      -  "type": "boolean"
      -}
  2. 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 supplied, the description carries the full burden. It does disclose the return shape (address, phone, 7-day hours, ratings, GPS/directions links) and the compact vs. rich output behavior, which is useful. It says nothing about auth/API-key requirements, rate limits, credit costs, or failure behavior of the provider chain.

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, zero filler: the first establishes what the tool does and what it returns, the second covers output density and the compact escape hatch. Return-value information is front-loaded where an agent will see it.

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 an 11-parameter tool with no output schema and no annotations, the description does the important work of describing what comes back and how verbosity changes it. Remaining gaps (provider failover, truncation via max_chars, credit implications of num_results) are covered by the schema descriptions, so overall it is adequate.

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 the baseline is 3. The description adds real meaning for one parameter only — it explains that compact 'keeps only title/rating/address', which the schema's enum text does not spell out. The other ten parameters (country, provider, min_rating, max_chars, etc.) get no additional semantics from the description.

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 Places / Maps search via Serper API') and scopes the result type to local businesses, which distinguishes it from generic siblings like search_web or search_news. It stops short of naming an alternative explicitly, but an agent can tell this is the places/local-business lookup.

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 implied by the 'local businesses' framing and the verbosity guidance, but there is no explicit when-to-use / when-not-to-use instruction or reference to sibling tools such as search_web for general queries. The agent must infer the routing decision.

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