Google Maps

resolve_names

Read-only

Resolves a batch list of specific location queries (landmark names or exact addresses) into canonical Google Maps Place IDs.

Input Requirements (CRITICAL):

queries (array of objects - MANDATORY): A list of location queries to resolve. You may specify up to 20 queries.
- Each query object must have:
  - text (string - MANDATORY): The text query representing a specific place name or address to resolve.
    - Examples: 'Googleplex, Mountain View, CA', '1600 Amphitheatre Pkwy, Mountain View, CA', 'Eiffel Tower, Paris'.
location_bias (object - OPTIONAL): Use this to prioritize results near a specific geographic area.
- Format: {"viewport": {"low": {"latitude": [value], "longitude": [value]}, "high": {"latitude": [value], "longitude": [value]}}}
region_code (string - OPTIONAL): The Unicode CLDR region code (two-letter country code, e.g., US, CA) of the user to bias the results.

Instructions for Tool Call:

Specificity (CRITICAL): Queries must represent a specific place name or address. General searches like 'restaurants' or chain names like 'Starbucks' are not supported.
Do NOT call this tool if the downstream tools you plan to invoke already accept raw address or place name strings directly.

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, 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 queries resolve successfully while others fail).
The output list of results is guaranteed to map 1:1 with the input queries indices. A failed query will result in an empty Result message (no entity is set) at its corresponding index in the results list.
You MUST check the failed_requests map field in the response to identify which specific query index failed. The key of failed_requests represents the 0-based index of the failed query in the request. Do not assume the entire batch call failed because of a partial failure.

Input Schema

TableJSON Schema

Name	Required	Description
`queries`	Yes	Required. A list of location queries to be resolved. You may specify up to 20 queries.
`regionCode`	No	Optional. An optional region code to bias the resolution results. If specified, the resolution results will be biased towards the entities that are in or near the specified region. This should be a CLDR region code. For example, "US" or "CA". Including `location_bias` or `region_code` often provides better results by narrowing the search space. If both `location_bias` and `region_code` are specified, `location_bias` takes precedence over `region_code`.
`locationBias`	No	Optional. An optional region to bias the resolution results. If specified, the resolution results will be biased towards the entities that are closer to this region. Including `location_bias` or `region_code` often provides better results by narrowing the search space. If both `location_bias` and `region_code` are specified, `location_bias` takes precedence over `region_code`.

Output Schema

TableJSON Schema

Name	Required	Description
`results`	No	Output only. The list of resolved entities from the location queries. Guaranteed to map 1:1 with the request `queries` indices. An empty string at index `i` indicates the resolution failed for that query. If the resolution failed, please check the `failed_requests` field for the error status.
`saveToMapsUrl`	No	Output only. A link to save all successfully resolved entities in Google Maps.
`failedRequests`	No	Output only. A map communicating partial failures. The key is the index of the failed request in the `queries` field. The value is the error status detailing why the resolution failed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

addedOutput schema / properties / saveToMapsUrl

Added value: +{
+  "description": "Output only. A link to save all successfully resolved entities in Google Maps.",
+  "readOnly": true,
+  "type": "string"
+}

AddedMay 18, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds real operational behavior beyond them: batch semantics, up to 20 queries, guaranteed 1:1 index mapping, and partial-failure handling via the failed_requests map. The save_to_maps_url instruction is also useful, though some of the return-value detail overlaps with the existing output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the headed sections are easy to scan, but the body is long and heavily redundant: it restates field names, examples, and limits that the schema already documents at 100% coverage, so several sentences do not earn their place for an agent that can read the schema.

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?

For a batch tool with an output schema, the description supplies everything needed to call it correctly and interpret results: mandatory vs optional inputs, the query cap, the 1:1 results-to-queries mapping, how to detect per-index failures, and how to surface save_to_maps_url. Nothing material 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%, so the baseline is 3, and the description largely mirrors the schema rather than extending it — the query examples, the 20-query limit, and the specificity rule all already appear in the LocationQuery and queries schema descriptions. The location_bias format example and the location_bias-over-region_code precedence note are the main additions.

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?

The first sentence states a specific verb (Resolves), input (batch list of location queries) and output (canonical Google Maps Place IDs), and the specificity constraint ('General searches like restaurants or chain names like Starbucks are not supported') implicitly separates it from search_places. Siblings such as resolve_maps_urls are never named, so the differentiation is inferential rather than explicit.

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?

It gives a clear when-to-use context plus a genuine when-not rule: 'Do NOT call this tool if the downstream tools you plan to invoke already accept raw address or place name strings directly,' and it warns that vague queries are unsupported. It stops short of naming the specific sibling to use instead (search_places, resolve_maps_urls), so the routing is implied rather than spelled out.

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

All Google Maps tools Inspect

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

Need Help?