Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_google_map_businesses_search

Search and filter stored Google Maps businesses by query, location, rating, reviews, and more. Retrieve business records with sorting options like relevance, rating, or distance.

Instructions

Search stored Google Maps businesses. Searches Google Maps business records stored in Elasticsearch. Sort enum: relevance, updated_at_desc, rating_desc, review_count_desc, distance_asc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text business search query, max 256 characters
categoryNoExact category filter, max 128 characters
countryNoExact country filter, max 128 characters
stateNoExact state filter, max 128 characters
countyNoExact county filter, max 128 characters
cityNoExact city filter, max 128 characters
townNoExact town filter, max 128 characters
min_ratingNoMinimum rating, 0 through 5
min_review_countNoMinimum review count
has_websiteNoFilter by website presence
has_phoneNoFilter by phone presence
latNoLatitude for radius filtering or distance sort
lonNoLongitude for radius filtering or distance sort
radius_mNoRadius in meters, 1 through 50000; requires lat and lon when supplied
sortNoSort enum: relevance, updated_at_desc, rating_desc, review_count_desc, distance_asc
pageNoPage number, defaults to 1
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
Behavior2/5

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

No annotations provided, so description carries full burden. Description states it searches Elasticsearch but lacks behavioral details like result limits, pagination behavior (though in schema), or side effects. No contradictions.

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?

Two concise sentences, no wasted words. Front-loaded with purpose. Efficient for scanning.

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?

Does not explain return structure, how filters combine, or any result ranking beyond sort. For a search tool with 17 params and no output schema, description is missing context but still minimally adequate.

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 baseline is 3. Description adds nothing beyond schema parameters; it lists sort enum which is already in schema. No additional meaning.

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?

Description clearly states the tool searches stored Google Maps businesses, using specific verb 'search' and resource 'business records'. It implies differentiation from siblings (facets, item, nearby, list) but does not explicitly distinguish them.

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?

No guidance on when to use this tool vs alternatives like the faceted search, item fetch, or nearby search. Does not specify when not to use or provide context for choosing this over siblings.

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