gmapsscraper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GMAPSSCRAPER_API_KEY | Yes | Your gmapsscraper API key. Get it at https://gmapsscraper.io/dashboard |
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 |
|---|---|
| scrape_google_mapsA | Search Google Maps and return business leads: name, address, phone, email, website, rating, reviews count, category, coordinates. Costs 2 credits per call — every call bills again (NOT idempotent, do not retry on your own). Always confirm with the user before spending credits. Multiple related keywords in one call cost the same 2 credits. Blocks until the scrape finishes (typically 30-120s). Be specific with keywords, e.g. "vegan restaurant in Brooklyn NY". |
| start_scrape_jobA | Submit a Google Maps scrape job without waiting for it to finish. Costs 2 credits per call — every call bills again (NOT idempotent, do not retry on your own). Always confirm with the user before spending credits. Returns a job id — poll it later with get_scrape_results. Use this instead of scrape_google_maps for large areas or when the user wants to continue working meanwhile. |
| get_scrape_resultsA | Check the status of a scrape job and fetch the business records once it is complete. Does not spend credits — safe to call repeatedly. |
| get_creditsA | Get the remaining gmapsscraper.io credit balance for the configured API key. Each scrape costs 2 credits. Free to call. |
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 4 tools
Each tool has a clearly distinct purpose: async job submission, result polling, credit checking, and synchronous scraping. The overlap between start_scrape_job and scrape_google_maps is explicitly addressed in the descriptions, making ambiguity minimal.
All tool names follow a consistent verb_noun pattern with snake_case (start_scrape_job, get_scrape_results, get_credits, scrape_google_maps), making the naming predictable and readable.
With 4 tools, the server is well-scoped for a focused Google Maps scraping service. Each tool serves an essential function without unnecessary redundancy.
The tool set covers the core lifecycle: asynchronous job creation and retrieval, synchronous scraping, and credit management. Minor gaps like job cancellation or listing are not critical for the primary use case.