Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

datasets_google_map_search

Search indexed Google Maps business records using filters for location, category, ratings, reviews, and more. Find businesses by query, sort by relevance or distance, and isolate service-area listings.

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).

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
countryNoExact country filter, max 128 characters
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.
has_websiteNoFilter by website presence
min_review_countNoMinimum review count

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
  2. 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."
  3. Addedv1.1.0

TDQS

A4.4/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 explains null rating and review_count semantics, the difference between null and 0, sort behavior for unrated businesses, and min_rating exclusion behavior. Minor omissions like rate limits or response shape are acceptable for a read-only search tool.

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 a single dense paragraph with all sentences contributing useful information. It is slightly long given the 18 parameters, but each sentence earns its place; there is no fluff or redundancy.

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?

Given the high parameter count and absence of annotations/output schema, the description covers parameter behavior comprehensively and explains edge-case semantics. It does not describe the return list shape, but this is a minor gap for a search tool whose primary purpose is clear from the schema and name.

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?

Even with 100% schema coverage, the description adds significant meaning: category can be localized/non-ASCII, rating null vs 0, rating_desc sorts unrated last, min_rating>0 excludes nulls, and has_geo=false for locationless businesses. These details go well beyond the schema property descriptions.

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 clearly states 'Search stored Google Maps businesses' and 'Searches Google Maps business records stored in a search index', which uses a specific verb+resource and 'stored' distinguishes it from live google_map_search and related dataset tools. It is unambiguous about its function.

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 practical guidance such as using the category facet to discover exact filter values and using has_geo=false to isolate locationless businesses. It does not explicitly say when to prefer this tool over sibling tools, but the 'stored' qualifier plus the facet suggestion provide useful context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server