Skip to main content
Glama
Sign In

SEO and Keyword Data API

by com.duoleads.keywords
OverviewDiscussionsAdmin

Google Maps places (up to 100)

google_maps_search
Read-onlyIdempotent

Google Maps places for a query in a country or around coordinates: up to 100 places with rank, name, category, address, phone, website, rating, review count, coordinates, price level and place id (no reviews or photos), from Google Maps, $0.018 a call. Use when building local-SEO or lead lists, or checking who ranks in a local search. No places is an empty answer, which is still charged. Bad input is a free 400; a data source failure is not charged. Price: $0.018 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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

Input Schema

NameRequiredDescriptionDefault
qYesWhat to look for (e.g. coffee shop), at most 200 characters.
numNoPlaces to return, 1-100. Default 20.
langNoLanguage code (with a country: one offered for it; with coordinates: a Google language code). Default: the country's main language when offered, else en.
countryNoISO 3166-1 alpha-2 country code (us, gb, de, ...; uk = gb). Default us. Leave out when coordinates are given.
coordinatesNoSearch around a point instead of a country: lat,lng or lat,lng,zoom: latitude -90..90, longitude -180..180 (up to 7 decimals), zoom 3-21 (default 14).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent/open-world; the description goes well beyond by disclosing that empty results are still billed, that invalid input yields a free 400, that a data-source failure is not charged, and that payment is passed via _meta["x402/payment"] as USDC on Base. Those are exactly the cost and failure-mode facts an agent needs before spending money on a call.

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-loaded with purpose, then fields, then use cases, then billing rules — a sound ordering. The price is stated twice ($0.018 a call, then a full 'Price: $0.018 per successful call' sentence), which is the one clearly redundant element.

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

Completeness5/5

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

For a paid, open-world lookup with no output schema, the description enumerates the returned fields, states the 100-place ceiling, and explains billing on empty/error paths plus the x402 payment channel. Nothing material an agent needs before invoking it is missing.

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 q, num, lang, country, and coordinates are all documented, including the country/coordinates exclusivity and the uk=gb alias. The description only restates the country-vs-coordinates choice at a high level, adding no syntax or format detail beyond the schema — the baseline 3 applies.

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?

Names a specific resource (Google Maps places) with its two search modes (query in a country or around coordinates) and enumerates every returned field, including the explicit exclusion of reviews and photos. An agent can distinguish this from google_search, bing_search, and youtube_search siblings purely from the text.

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 use cases — local-SEO research, lead-list building, checking who ranks in a local search — which maps well onto the sibling set. It stops short of naming an alternative (e.g., 'use google_search for general web results, this for local packs') or stating when not to use it.

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

All SEO and Keyword Data API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources