maps-fetcher-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAPS_FETCHER_ROOT | No | Override the root directory for output. Default is /mnt/d/Projects/maps-data-fetcher/places (WSL layout). |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_maps_placeA | Fetch a Google Maps place by link (maps.app.goo.gl/... or full google.com/maps URL). Downloads gallery media at max resolution plus business metadata (name, phone, website, rating, address, plus code, hours, coordinates). Args: url: Google Maps place link (single place only, not search links). output_dir: optional root directory (default: /mnt/d/Projects/maps-data-fetcher/places). A per-place subfolder is created with photos/, videos/, info_pw.json, contact_sheet.jpg. include: "all" (default) | "info" (metadata only, fast) | "photos" | "videos" | "media" (photos+videos). meta_only: deprecated alias for include="info". Returns JSON summary: place data, media counts, output paths. Typical run: info ~20-40s, full fetch 60-220s. |
| get_place_infoA | Fast metadata-only fetch: name, phone, website, rating, address, plus code, hours, coordinates. No media downloaded. Use when the agent only needs business info. ~20-40s. |
| get_place_mediaA | Media-only fetch: downloads gallery photos and/or videos, skips verbose metadata in the response. Use when the agent only needs the images/videos. Args: kind: "both" (default) | "photos" | "videos". Returns JSON: place name, counts, output dirs. |
| list_maps_placesC | List previously fetched places under the output root with photo/video counts and metadata. |
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
There is significant overlap: fetch_maps_place with include='info' does exactly what get_place_info does, and with include='media' does what get_place_media does. While the descriptions clarify the intended use cases, an agent may struggle to pick the right tool since fetch_maps_place is a superset. The tools are not clearly distinct in purpose.
The naming mixes conventions: 'get_place_info' and 'get_place_media' follow a get_place_N pattern, but 'fetch_maps_place' uses a different verb (fetch) and noun order, and 'list_maps_places' uses plural. The pattern is not consistent across all tools, though the tools are readable.
At 4 tools, the server is well-scoped for a maps fetcher. However, the presence of get_place_info and get_place_media is redundant given fetch_maps_place can achieve the same via its include parameter, suggesting the count could be trimmed to 2–3 tools without losing functionality.
The core lifecycle for fetching Google Maps place data is covered: retrieving metadata, media, or both, plus listing previously fetched places. There are no obvious dead ends for the stated purpose. Missing delete/update operations are not essential for a fetcher, so the surface feels complete.