Skip to main content
Glama

Google Maps

by com.googleapis.mapstools
OverviewDiscussionsAdmin

resolve_maps_urls

Read-only

Resolves a list of Google Maps URLs into canonical Google Maps Place IDs.

When to call this tool (CRITICAL):

Input Requirements (CRITICAL):

  • urls (array of strings - MANDATORY): The list of Google Maps URLs to resolve. Each URL must be a valid, single-place Google Maps URL.

Save to Google Maps:

  • The response includes a save_to_maps_url field: a single Google Maps link containing all successfully resolved places.

  • When the user wants to save, share, or open the resolved places as a list in Google Maps (e.g. collecting places shared in a conversation), present this link to the user. Do NOT construct this link yourself.

Error Handling (CRITICAL):

  • This is a batch processing tool. A request might return "mixed results" (e.g. some URLs resolve successfully while others fail).

  • The output list of entities is guaranteed to map 1:1 with the input urls indices. A failed URL resolution will result in an empty Entity message (no fields are set) at its corresponding index in the entities list.

  • You MUST check the failed_requests map field in the response to identify which specific URL index failed. The key of failed_requests represents the 0-based index of the failed URL in the request. Do not assume the entire batch call failed because of a partial failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesRequired. The Google Maps URLs to be resolved. Each URL should be a valid Google Maps URL, for example, https://maps.app.goo.gl/..., https://www.google.com/maps/place/..., or https://maps.google.com/.... Currently, only URLs pointing to a single place are supported. You may specify up to 20 URLs.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
entitiesNoOutput only. The list of resolved entities from the Google Maps URLs. Guaranteed to map 1:1 with the request `urls` indices. An empty message at index `i` (where no `entity` is set) indicates the resolution failed for that URL. If the resolution failed, please check the `failed_requests` field for the error status.
saveToMapsUrlNoOutput only. A link to save all successfully resolved entities in Google Maps.
failedRequestsNoOutput only. A map communicating partial failures for the Google Maps URLs. The key is the index of the failed request in the `urls` field. The value is the error status detailing why the resolution failed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / saveToMapsUrl
      Added value: +{
+  "description": "Output only. A link to save all successfully resolved entities in Google Maps.",
+  "readOnly": true,
+  "type": "string"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, the description discloses high-value non-obvious behavior: this is a batch tool that can return mixed results, entities map 1:1 by index, failed entries appear as empty Entity messages, and failed_requests keys map to 0-based input indices. It also warns not to treat partial failure as total failure and not to hand-construct the save link.

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?

Headers and bold labels front-load the critical routing and error-handling guidance, and the error section is well-structured. It loses a point for the 'Input Requirements' block, which duplicates schema content verbatim rather than earning its space.

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

Completeness5/5

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

Even though an output schema exists, the description supplies the interpretation an agent needs for correct use of that output (index alignment, empty Entity on failure, failed_requests keyed by index) plus the save_to_maps_url workflow. Nothing needed to call or consume the result is missing.

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% and there is a single parameter, so the schema already documents format, examples, and the 20-URL cap. The description's 'Input Requirements' block largely restates that schema text, adding no syntax or semantics beyond it — baseline 3 applies.

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 first sentence states a specific verb, resource, and output ('Resolves a list of Google Maps URLs into canonical Google Maps Place IDs'), so the transformation is unambiguous. It is clearly differentiable from siblings like resolve_names, search_places, and compute_routes without opening any schema.

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

Usage Guidelines4/5

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

The 'When to call this tool (CRITICAL)' section gives a concrete trigger (user provides maps.app.goo.gl / google.com/maps/place links) and states the batch limit. It does not explicitly name sibling alternatives or when NOT to use it (e.g. vs. search_places for non-URL queries), leaving that to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Google Maps toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources