Skip to main content
Glama

SEO and Keyword Data API

Business listings by name or category (up to 50)

business_listings
Read-onlyIdempotent

Businesses listed on Google Maps by name and/or category in a country, optionally within a radius of a point: up to 50 with name, category, address, phone, website, rating, review count, coordinates, price level and place id (no reviews or photos), from Google Maps business listings, $0.08 a call. Use when building local lead lists or auditing a market. No match is an empty answer, still charged. Bad input is a free 400; a data source failure is not charged. Price: $0.08 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": {
      "country": "<country>"
    },
    "name": "business_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords in the business name (at most 100 characters). q or category is required.
limitNoRows to return, 1-50. Default 20.
countryYesISO 3166-1 alpha-2 country code of the businesses (us, gb, de, ...).
categoryNoA Google business category id, lower case with underscores (pizza_restaurant, coffee_shop, dentist, ...).
coordinatesNoOnly businesses within a radius of a point: lat,lng,radius: latitude -90..90, longitude -180..180 (up to 7 decimals), radius 1-100 km (whole number; default 10).

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.1/5.0
Behavior5/5

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

Annotations already cover the read-only, open-world, idempotent safety profile, yet the description adds substantial context on top: a hard 50-result cap, an explicit list of returned fields with reviews and photos excluded, and a full cost model. Charging semantics are unusually well disclosed — $0.08 per successful call, empty results still billed, 400s free, data-source failures not billed — plus the x402/USDC-on-Base payment requirement passed via _meta.

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?

The result shape and scope are front-loaded in the first sentence, with cost and payment details pushed to the end where they belong. The opening sentence is long and packs enumeration, exclusions, provenance and price into one breath, but nearly every clause carries information an agent needs.

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?

There is no output schema, and the description compensates by enumerating the returned fields and noting the omission of reviews and photos. Combined with the cost, error and payment details, nothing material is missing for a 5-parameter paid query tool.

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 the schema already documents q, category, country, limit and coordinates formats. The description adds the combinatorial semantics ('by name and/or category' and 'within a radius of a point'), which helps clarify that q and category can be combined, but contributes no format or edge-case detail beyond the schema.

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 gives a specific verb and resource — businesses listed on Google Maps by name and/or category, scoped to a country with an optional radius — plus the exact output columns and the 50-row cap. An agent can tell what data comes back. It does not, however, distinguish itself from the sibling google_maps_search, which sounds like the closest alternative.

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?

It states concrete contexts for use ('building local lead lists or auditing a market'), which is more than most tools offer. It stops short of exclusions — there is no statement of when to use google_maps_search instead, or when a radius query is inappropriate.

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.