Skip to main content
Glama

SteadyScrape Local Leads

Find local businesses (Google Maps)

find_local_businesses
Read-only

Businesses listed on Google Maps for 1-5 categories in an area (city, postal code, country, or coordinates with a radius), with optional lead filters: no website, unclaimed profile, rating below a value, fewer reviews than a value, or first listed in the last N days. Returns name, category, address, coordinates, Google Maps link and place_id, website, claimed flag, rating, review count, status and first-seen date. Phone numbers are not returned. Billed per business returned plus a run start fee.

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": {
      "categories": "<categories>"
    },
    "name": "find_local_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity as written in addresses, e.g. Austin. Use with country_code.
limitNoBusinesses to return (default 20, max 50). Billed per business returned.
sort_byNoOrder when more businesses match than the limit (default most_reviews).
websiteNoWebsite filter (default any).
radius_kmNoRadius around coordinates in km (default 10).
categoriesYes1-5 Google Maps categories, e.g. plumber, dentist, roofing contractor, restaurant.
min_ratingNoOnly businesses rated at least this.
coordinatesNoSearch around a point "lat,lng", e.g. 30.2672,-97.7431. Use with radius_km.
min_reviewsNoOnly businesses with at least this many reviews.
postal_codeNoExact postal code, e.g. 78704.
country_codeNo2-letter ISO country code, e.g. US, GB, CA. Can be used alone for a country-wide list.
rating_belowNoOnly businesses rated strictly below this, e.g. 4.
include_hoursNoInclude weekly opening hours (default false).
reviews_belowNoOnly businesses with fewer reviews than this (zero-review businesses included).
unclaimed_onlyNoOnly businesses whose Google profile is unclaimed (default false).
business_statusNoDefault operating.
first_seen_within_daysNoOnly listings first found by the data provider in the last N days (not the opening date).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark it read-only, open-world and non-idempotent, and the description adds genuinely new operational facts beyond them: billing is per business returned plus a run start fee, and phone numbers are not returned. It also enumerates the returned fields, which matters since there is no output schema. That is substantive disclosure, not repetition.

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?

Three sentences, front-loaded with purpose, then filters, then returns, then the billing and phone caveats. Every sentence carries distinct information; nothing is redundant padding.

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 17-parameter tool with no output schema, the description covers what an agent needs: how to define the area, what the filters mean collectively, the exact returned field set, a data limitation (no phone numbers), and the cost model. The only untouched item is auth/rate-limit behavior, which is minor here.

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 description coverage is 100%, so the baseline is 3, and the description does add interpretive value by grouping the negative-signal filters (no website, unclaimed, rating below, few reviews, recently first seen) into a coherent lead-generation concept. It also restates that 'first listed' means provider first-seen rather than opening date. It adds framing rather than new per-parameter syntax, so 4 rather than 5.

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?

The description opens with a specific verb and resource: businesses listed on Google Maps, scoped to 1-5 categories within a geographic area, plus optional lead filters. That scope (a discovery/listing tool) is plainly distinct from the review-oriented siblings business_reviews and review_summary, so an agent can route without opening a schema.

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 gives concrete guidance on how to invoke it: an area is a city with country_code, an exact postal code, or coordinates with radius_km, and country_code alone yields a country-wide list. It also frames the optional filters as a 'lead filter' use case. It stops short of explicit when-not-to-use or naming a sibling alternative, which keeps it at 4.

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.

Resources