Skip to main content
Glama
Sign In

Google Maps

by com.googleapis.mapstools
OverviewDiscussionsAdmin

search_places

Read-only

Call this tool when the user's request is to find places, businesses, addresses, locations, points of interest, or any other Google Maps related search.

Input Requirements (CRITICAL):

  1. text_query (string - MANDATORY): The primary search query. This must clearly define what the user is looking for.

    • Examples: 'restaurants in New York', 'coffee shops near Golden Gate Park', 'SF MoMA', '1600 Amphitheatre Pkwy, Mountain View, CA, USA', 'pets friendly parks in Manhattan, New York', 'date night restaurants in Chicago', 'accessible public libraries in Los Angeles'.

    • For specific place details: Include the requested attribute (e.g., 'Google Store Mountain View opening hours', 'SF MoMa phone number', 'Shoreline Park Mountain View address').

  2. location_bias (object - OPTIONAL): Use this to prioritize results near a specific geographic area.

    • Format: {"location_bias": {"circle": {"center": {"latitude": [value], "longitude": [value]}, "radius_meters": [value (optional)]}}}

    • Usage:

      • To bias to a 5km radius: {"location_bias": {"circle": {"center": {"latitude": 34.052235, "longitude": -118.243683}, "radius_meters": 5000}}}

      • To bias strongly to the center point: {"location_bias": {"circle": {"center": {"latitude": 34.052235, "longitude": -118.243683}}}} (omitting radius_meters).

  3. language_code (string - OPTIONAL): The language to show the search results summary in.

    • Format: A two-letter language code (ISO 639-1), optionally followed by an underscore and a two-letter country code (ISO 3166-1 alpha-2), e.g., en, ja, en_US, zh_CN, es_MX. If the language code is not provided, the results will be in English.

  4. region_code (string - OPTIONAL): The Unicode CLDR region code of the user. This parameter is used to display the place details, like region-specific place name, if available. The parameter canaffect results based on applicable law.

    • Format: A two-letter country code (ISO 3166-1 alpha-2), e.g., US, CA.

Instructions for Tool Call:

  • Location Information (CRITICAL): The search must contain sufficient location information. If the location is ambiguous (e.g., just "pizza places"), you must specify it in the text_query (e.g., "pizza places in New York") or use the location_bias parameter. Include city, state/province, and region/country name if needed for disambiguation.

  • Always provide the most specific and contextually rich text_query possible.

  • Only use location_bias if coordinates are explicitly provided or if inferring a location from a user's known context is appropriate and necessary for better results.

  • The grounded output must be attributed to the source using the information from the attribution field when available.

Input Schema

NameRequiredDescriptionDefault
pageSizeNoOptional. The maximum number of places to return, up to 5. The service may return fewer than this value. The default value is 5.
textQueryYesRequired. The text query.
regionCodeNoOptional. The Unicode country/region code (CLDR) of the location where the request is coming from. This parameter is used to display the place details, like region-specific place name, if available. The parameter can affect results based on applicable law. For example, "US" for United States. For more information, see https://www.unicode.org/cldr/charts/latest/supplemental/territory_language_information.html. Note that 3-digit region codes are not currently supported.
languageCodeNoOptional. The language to request that the summary is returned in. If the language code is unspecified or unrecognized, the summary with a preference for English will be returned. For example, "en" for English. Current list of supported languages: https://developers.google.com/maps/faq#languagesupport.
locationBiasNoAn optional region to bias the search results to. If an explicit location is in `text_query`, it will be used to bias the search results instead of this field.
includeExtendedDetailsNoOptional. Includes extended place details in the response. Set this field to `true` when the user request requires rich qualitative insights, real-time dynamics, or specialized entity attributes: - Qualitative reviews, customer sentiment, and feedback. - Specific offerings like menu items, dishes, food specialties, beverages, or business highlights. - Qualitative atmosphere, interior decor, aesthetic, ambience, or mood. - Real-time data and specialized facility specs, visitor policies/tips, wait times. Leave `false` (default) for standard discovery searches (e.g., cuisines, store types), location/address lookups, contact info, operating hours, and standard metadata/amenities. Enabling this field will incur higher latency.

Output Schema

NameRequiredDescriptionDefault
placesNoOutput only. The list of places that are mentioned in the summary.
summaryNoOutput only. A natural language summary of the search results. The summary may contain zero-based citations like "[0]", "[1]", "[2]" etc. These citations map to the corresponding places in the `places` field.
contentTokenNoOutput only. An encrypted token that encapsulates the search context and can be passed to Google Maps visual rendering services, SDKs, or the Maps Agentic UI Toolkit (A2UI) to display interactive UI components for the returned search results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / contentToken
      Added value: +{
+  "description": "Output only. An encrypted token that encapsulates the search context and can be passed to Google Maps visual rendering services, SDKs, or the Maps Agentic UI Toolkit (A2UI) to display interactive UI components for the returned search results.",
+  "readOnly": true,
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / includeExtendedDetails
      Added value: +{
+  "description": "Optional. Includes extended place details in the response. Set this field to `true` when the user request requires rich qualitative insights, real-time dynamics, or specialized entity attributes: - Qualitative reviews, customer sentiment, and feedback. - Specific offerings like menu items, dishes, food specialties, beverages, or business highlights. - Qualitative atmosphere, interior decor, aesthetic, ambience, or mood. - Real-time data and specialized facility specs, visitor policies/tips, wait times. Leave `false` (default) for standard discovery searches (e.g., cuisines, store types), location/address lookups, contact info, operating hours, and standard metadata/amenities. Enabling this field will incur higher latency.",
+  "type": "boolean"
+}
    • addedInput schema / properties / pageSize
      Added value: +{
+  "description": "Optional. The maximum number of places to return, up to 5. The service may return fewer than this value. The default value is 5.",
+  "format": "int32",
+  "type": "integer"
+}
  3. Changed2 schema fields changed
    • addedOutput schema / $defs / Attribution
      Added value: +{
+  "description": "Required attribution to show with maps content.",
+  "properties": {
+    "title": {
+      "description": "The title to display for the attribution.",
+      "type": "string"
+    },
+    "url": {
+      "description": "The URL to link to for the attribution.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / $defs / PlaceView / properties / attribution
      Added value: +{
+  "$ref": "#/$defs/Attribution",
+  "description": "Required attribution to show with the place."
+}
  4. First observed

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 (readOnly, non-destructive), so the description adds the operational rules that matter: the search must contain sufficient location context or results degrade, and grounded output must be attributed using the `attribution` field. It also warns that verbose-detail requests add latency, though the schema description already states this. No contradiction with annotations.

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 trigger condition is correctly front-loaded, but the body is long and heavily formatted with duplicated guidance (location requirements appear in both the numbered list and the 'Instructions' section). Several paragraphs restate schema text verbatim (language_code/region_code formats), diluting the parts that carry new information.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description covers the main decision points: query formulation, location disambiguation, and when to request extended details. The one gap is that pageSize (maximum 5) is never acknowledged in the description, and the parameter-name mismatch above slightly undermines otherwise solid completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description actively introduces naming that does not match the schema: it refers to `text_query`, `location_bias`, `language_code`, `region_code` instead of textQuery/locationBias/languageCode/regionCode, and its location_bias example uses `radius_meters` where the schema defines `radiusMeters`. An agent copying that example would emit invalid arguments. The text_query example list is genuinely helpful, but the mismatched keys are a net risk rather than added meaning.

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 opening sentence names a specific verb and resource ('find places, businesses, addresses, locations, points of interest') and scopes it to Google Maps search, which no sibling (compute_routes, lookup_weather, resolve_names, resolve_maps_urls) covers. An agent can route a 'find X near Y' request here without opening the 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?

Gives an explicit trigger condition ('when the user's request is to find places...'), a rule that location must be resolvable either in text_query or via location_bias, and a constraint that location_bias should only be used with explicit coordinates or well-known user context. It never names a sibling tool as an alternative, so the boundary with resolve_names / resolve_maps_urls is left implicit.

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