Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_google_map_search

Find stored Google Maps businesses by keyword, location, category, rating, phone, website, and closure status to target leads or analyze local markets.

Instructions

Search stored Google Maps businesses. Searches Google Maps business records stored in a search index. Sort enum: relevance, updated_at_desc, rating_desc, review_count_desc, distance_asc. category is the exact Google Maps category label returned for the business locale; it can be localized, non-ASCII, or contain punctuation, so use the category facet to discover exact filter values. A rating of null means no aggregate rating is available. A review_count of null means Google did not return a count; numeric 0 means Google confirmed zero reviews. rating_desc sorts unrated businesses last, and min_rating above 0 excludes them. Use has_geo=false to isolate locationless service-area businesses (which have a null geo). A permanently_closed of true means Google marks the business permanently closed; false means a crawl confirmed it does not; null means the business has not been status-checked since capture shipped on 2026-08-31 and is UNKNOWN, not open — so any total computed from this dataset includes an unknown number of closed businesses. Use permanently_closed=false to exclude the confirmed-closed ones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text business search query, max 256 characters
latNoLatitude for radius filtering or distance sort
lonNoLongitude for radius filtering or distance sort
cityNoExact city filter, max 128 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, updated_at_desc, rating_desc, review_count_desc, distance_asc
townNoExact town filter, max 128 characters
stateNoExact state filter, max 128 characters
countyNoExact county filter, max 128 characters
countryNoCountry filter. Accepts the full English name (\
has_geoNoFilter by location presence: true keeps only mappable businesses with coordinates; false isolates locationless service-area businesses that have no map location
categoryNoExact locale-specific Google Maps category label; use the category facet to discover values, max 128 characters
radius_mNoRadius in meters, 1 through 50000; requires lat and lon when supplied
has_phoneNoFilter by phone presence
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
min_ratingNoMinimum rating, 0 through 5. Businesses with no aggregate Google rating are returned with rating null, so any min_rating above 0 excludes them.
state_codeNoExact ISO 3166-2 state/region code filter, e.g. US-CA or FR-HDF, max 128 characters; use facet=state_code to discover values
county_codeNoExact ISO 3166-2 county/district code filter, e.g. FR-59 or IT-RM, max 128 characters; use facet=county_code to discover values
has_websiteNoFilter by website presence
min_review_countNoMinimum review count
permanently_closedNoClosure filter. true keeps only businesses Google marks Permanently closed; false excludes them, keeping every business not known to be closed. Most rows have never been status-checked and are returned with permanently_closed null, which means unknown, not open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "updated_at_desc",
+  "rating_desc",
+  "review_count_desc",
+  "distance_asc"
+]
  2. Changed4 schema fields changedv1.16.2
    • changedInput schema / properties / country / description
      Previous value: -"Exact country filter, max 128 characters"New value: +"Country filter. Accepts the full English name (\\"
    • addedInput schema / properties / county_code
      Added value: +{
+  "description": "Exact ISO 3166-2 county/district code filter, e.g. FR-59 or IT-RM, max 128 characters; use facet=county_code to discover values",
+  "type": "string"
+}
    • addedInput schema / properties / permanently_closed
      Added value: +{
+  "description": "Closure filter. true keeps only businesses Google marks Permanently closed; false excludes them, keeping every business not known to be closed. Most rows have never been status-checked and are returned with permanently_closed null, which means unknown, not open.",
+  "type": "boolean"
+}
    • addedInput schema / properties / state_code
      Added value: +{
+  "description": "Exact ISO 3166-2 state/region code filter, e.g. US-CA or FR-HDF, max 128 characters; use facet=state_code to discover values",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Exact category filter: a Google Maps type token in lower-case snake_case (e.g. dentist, bus_stop), max 128 characters"New value: +"Exact locale-specific Google Maps category label; use the category facet to discover values, max 128 characters"
  4. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / category / description
      Previous value: -"Exact category filter, max 128 characters"New value: +"Exact category filter: a Google Maps type token in lower-case snake_case (e.g. dentist, bus_stop), max 128 characters"
    • addedInput schema / properties / has_geo
      Added value: +{
+  "description": "Filter by location presence: true keeps only mappable businesses with coordinates; false isolates locationless service-area businesses that have no map location",
+  "type": "boolean"
+}
    • changedInput schema / properties / min_rating / description
      Previous value: -"Minimum rating, 0 through 5"New value: +"Minimum rating, 0 through 5. Businesses with no aggregate Google rating are returned with rating null, so any min_rating above 0 excludes them."
  5. Addedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and handles it well. It discloses nuanced data behaviors: null vs 0 review_count semantics, null geo for service-area businesses, the unknown-closure meaning of permanently_closed null, and the dataset-wide caveat that totals include an unknown number of closed businesses.

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 description is dense but every sentence carries operational weight. The only flaw is mild redundancy in the first two sentences ('Search stored Google Maps businesses' and 'Searches Google Maps business records stored in a search index'), which repeats the same idea. Otherwise it is well-structured and front-loaded with the core purpose.

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 a 21-parameter search tool with no output schema and no annotations, the description covers the critical query semantics: sort behavior, category discovery, null-handling, geo filtering, and closed-status interpretation. It does not describe return fields or pagination defaults, but the schema already documents page/page_size, and the dataset caveats are well covered.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds substantial meaning beyond the schema: cross-parameter interaction between sort, rating null, and min_rating; the locale-specific nature of category values with a pointer to the facet; and the tri-state semantics of permanently_closed that mere enum definition cannot convey.

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 states a specific verb and resource: 'Search stored Google Maps businesses.' The word 'stored' distinguishes it from live Google Maps tools like google_map_search or google_map_place, so an agent can tell it apart without opening the 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?

The description gives clear operational context: how `rating_desc` treats unrated businesses, when `min_rating` excludes them, when to use `has_geo=false`, and how to interpret `permanently_closed` null. It does not explicitly name alternative tools or when-not-to-use cases, but the guidance is concrete and actionable.

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

Deploy Server

Other Tools