Skip to main content
Glama

google_maps_business_search

Local businesses from a Maps search — name, address, phone, website, rating, hours, place id. Flat 2 credits. Add enrich=contacts for role emails and socials from each website. Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

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": {
      "q": "<q>"
    },
    "name": "google_maps_business_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesKeyword, for example plumber or coffee. Min 2 characters.
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
limitNoMax businesses to return (default 20, max 100). Not a page cursor — there is no next page. Flat 2 credits per call; zero businesses is 0 credits.
enrichNoSet to contacts to add a contacts object (role emails, E.164 phones, social profiles, contactPageUrl, blockedByRobots) to each business that has a website. limit is at most 50 with enrich=contacts. +1 credit per distinct domain where contacts are found; 0 for the rest. Omit for the plain search.
fieldsNoOptional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.
compactNoDefault true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body.
languageNoLanguage code, for example en. Default en.
locationNoPlace name: City, Country or City, Region, Country — for example Austin, TX, Istanbul, Turkey, Paris, France, or a country such as Germany. Case, accents, US state codes, and country aliases (USA, UK, Turkey) are handled. A city name shared by several places (Paris) returns 400 with suggestions. When set, the locationCode parameter is ignored.
locationCodeNoNumeric place code, used only when location is omitted. Default 2840 (United States).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body."New value: +"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body."
  2. Changed1 schema field changed
    • addedInput schema / properties / enrich
      Added value: +{
      +  "description": "Set to contacts to add a contacts object (role emails, E.164 phones, social profiles, contactPageUrl, blockedByRobots) to each business that has a website. limit is at most 50 with enrich=contacts. +1 credit per distinct domain where contacts are found; 0 for the rest. Omit for the plain search.",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "default": true,
      +  "description": "Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Optional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max businesses to return (default 20, max 100). Not a page cursor — there is no next page. Flat 2 credits on every successful call, including zero businesses."New value: +"Max businesses to return (default 20, max 100). Not a page cursor — there is no next page. Flat 2 credits per call; zero businesses is 0 credits."
  5. Changed1 schema field changed
    • changedInput schema / properties / location / description
      Previous value: -"Place name as City,Region,Country, for example Austin,Texas,United States. When set, locationCode is not used and is left out of the response. A free-text city alone (austin) is not a place name."New value: +"Place name: City, Country or City, Region, Country — for example Austin, TX, Istanbul, Turkey, Paris, France, or a country such as Germany. Case, accents, US state codes, and country aliases (USA, UK, Turkey) are handled. A city name shared by several places (Paris) returns 400 with suggestions. When set, the locationCode parameter is ignored."
  6. Changed1 schema field changed
    • changedInput schema / properties / location / description
      Previous value: -"Place name as City,Region,Country, for example Austin,Texas,United States. When set, locationCode is ignored. A free-text city alone (austin) is not a place name."New value: +"Place name as City,Region,Country, for example Austin,Texas,United States. When set, locationCode is not used and is left out of the response. A free-text city alone (austin) is not a place name."
  7. Added

TDQS

A3.8/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 well: it discloses the flat 2-credit price, +1 credit per distinct domain for enrich, that empty results and failures are never charged, and that caching defaults to fresh. It omits auth/permission requirements and any rate limits, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads what the tool returns, then the pricing and option modifiers — good ordering and no filler. The price is stated twice ('Flat 2 credits.' and 'Costs 2 credits.'), which is a small redundancy in an otherwise tight description.

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?

Nine parameters, no annotations, and no output schema, yet the description covers return fields, billing rules, failure billing, caching behavior, and the enrich modifier — enough to call it correctly and predict cost. Remaining gaps are auth requirements and whether enrich changes the result shape beyond adding a contacts object.

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

Parameters4/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, but the description adds cost semantics the schema does not: enrich=contacts is billed per domain, cache=true yields a 0-credit hit, and the plain search is the default. It does not add much on q, language, location, or fields beyond what the schema already says.

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?

Opens with a specific verb+resource ('Local businesses from a Maps search') and enumerates the returned fields — name, address, phone, website, rating, hours, place id — so an agent knows exactly what comes back. It does not name or contrast any sibling, though the sibling set is mostly other platforms, so confusion risk is low.

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?

Gives conditional guidance for options (enrich=contacts for emails/socials, cache=true for a free cache hit, default fresh) but never states when to choose this tool over an alternative search tool, nor any when-not conditions. Usage is implied rather than prescribed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.