Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_google_map_search

Search stored Google Maps businesses by query, location, category, rating, and more. Filter results to find mappable or locationless businesses with specific criteria.

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 a Google Maps type token in lower-case snake_case (e.g. dentist, bus_stop, atm), both as the category filter and in each result's category field. A rating of null means no aggregate rating is available for that business (too few reviews, or a place type Google does not rate) — it is never a literal zero-star score; read it together with review_count, and note that 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 category filter: a Google Maps type token in lower-case snake_case (e.g. dentist, bus_stop), 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
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses important behaviors: null rating meaning, sorting behavior for unrated businesses, category format, and locationless businesses via has_geo. However, it does not mention pagination constraints or rate limits, which are relevant but partially covered in schema.

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 concise (5 sentences) and front-loaded with the purpose. It packs useful details without being verbose, though a slightly more structured format (e.g., bullet points) could improve scanability.

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

Completeness3/5

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

Given the absence of an output schema, the description explains key fields (category, rating, geo) but does not describe the overall response structure or default pagination. It covers essential nuances but leaves some gaps in completeness.

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 coverage is 100%, so baseline is 3. The description adds semantic value beyond the schema by explaining the sort enum values' effects on ratings, the category format as snake_case tokens, and the significance of null ratings. It also clarifies has_geo filtering for service-area businesses.

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 the tool searches stored Google Maps businesses with specific verbs and resources. It adds value by explaining the sort enum, category format, rating null handling, and has_geo usage, which distinguishes it from siblings like google_map_search or datasets_google_map_item.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives (e.g., live Google Maps search or nearby/facets tools). It provides context for has_geo=false but lacks guidance on when not to use it or comparative usage scenarios.

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