gmaps-lead-atlas-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_MAPS_API_KEY | Yes | Your Google Maps API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_businessesA | Search Google Maps for businesses matching a query, with lead-qualification filters. IMPORTANT: Google ranks results by prominence, which correlates strongly with having a website and many reviews. Businesses lacking a website or phone are therefore ranked LAST and often fall outside the 60-result ceiling. A small result count under has_website:false means the view is truncated, NOT that few such businesses exist. Use sweep_area for representative coverage of a city or region. |
| get_business_detailsA | Fetch full Google Maps details for up to 10 businesses by place ID. Returns opening hours, all phone formats, address components, reviews and business status. Costs one API call per place ID — use search_businesses first to narrow the list. |
| sweep_areaA | Search an entire city or region by tiling it into overlapping circular searches, then deduplicating. Use this instead of search_businesses when you need representative coverage rather than the top results. A plain search returns at most 60 results ranked by prominence; this applies that ceiling per tile instead. COST: this issues roughly one to three API calls per tile. max_tiles defaults to 25. Raise max_tiles for better coverage and higher cost. Every response reports the exact call count. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: search_businesses for targeted queries with filters, sweep_area for tiled regional coverage, and get_business_details for fetching full details by place ID. The descriptions explicitly clarify when to use each, leaving no ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case: search_businesses, sweep_area, get_business_details. The verbs are clear and the pattern is uniform.
Three tools is well-scoped for a Google Maps lead-gen server. Each tool covers a necessary part of the workflow—search, area sweep, and details—without unnecessary overlap or bloat.
The tool surface covers the full lead-generation flow: finding businesses via search or area sweep, then retrieving detailed information including reviews and status. There are no obvious gaps for the stated purpose.