Vee3

google-maps.nearby_search

Search for places near a latitude and longitude.

Required: location. Optional: radius (defaults to 1000 meters when sort_by is Relevance), keyword, place_type, open_now, min_price, max_price, language, region, and cursor. When sort_by is Distance, omit radius and provide keyword or place_type. Pass cursor from a previous cursor_next to fetch the next page.

Returns matching places in places. Use place_id with place detail, review, and photo endpoints.

cursor_next and cursor_previous appear only when pagination cursors are available. Additional upstream fields may appear.

Cost = 10 tokens.

Input Schema

TableJSON Schema

Name	Required	Description
`cursor`	No	Pagination cursor from cursor_next on a previous response.
`radius`	No	Search radius in meters (default 1000).
`region`	No	Two-character region code (for example us). On search endpoints this biases results by ccTLD. On place endpoints this selects regional place data.
`keyword`	No	Keyword to match nearby places (for example restaurant).
`sort_by`	No	Result ordering: "Relevance" (default) or "Distance".
`language`	No	Language code for results (for example en).
`location`	Yes	Latitude and longitude of the search point (for example 40,-110).
`open_now`	No	When true, return only places open for business at query time.
`max_price`	No	Maximum price level (0–4, inclusive).
`min_price`	No	Minimum price level (0–4, inclusive).
`place_type`	No	Restrict results to a single Google Maps place type (for example restaurant).

Output Schema

TableJSON Schema

Name	Required	Description
`places`	No	Nearby places matching the search criteria. Additional upstream fields may appear.
`cursor_next`	No	Cursor for the next page when more results are available.
`cursor_previous`	No	Cursor for the previous page when available.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedJul 3, 2026

changedOutput schema / $defs / GoogleMapsNearbySearchResponsePlacesItem / properties / rating / anyOf

Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / $defs / GoogleMapsNearbySearchResponsePlacesItemLocation / properties / latitude / anyOf

Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / $defs / GoogleMapsNearbySearchResponsePlacesItemLocation / properties / longitude / anyOf

Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedJun 22, 2026

changedOutput schema / $defs / GoogleMapsNearbySearchResponsePlacesItem / properties / types / anyOf

Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/GoogleMapsNearbySearchResponsePlacesItemTypesItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / $defs / GoogleMapsNearbySearchResponsePlacesItemTypesItem

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "type": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Place type label.",
-      "title": "Type"
-    }
-  },
-  "title": "GoogleMapsNearbySearchResponsePlacesItemTypesItem",
-  "type": "object"
-}

First observedJun 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description takes on the burden of behavioral disclosure. It goes beyond the schema by explaining default radius behavior dependent on sort_by, when pagination cursors appear, and the token cost. It does not discuss authentication or rate limits, but for a search tool this is acceptable.

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?

The description is a single well-structured paragraph with clear sections: purpose, required/optional, usage rule, output, and cost. It is front-loaded with the main purpose and avoids unnecessary filler. Slight redundancy with schema (e.g., default radius) but earns its place with the conditional logic.

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?

Given the presence of an output schema, return values are covered there. The description adds critical context about pagination, the 'places' response key, and downstream use of place_id. It does not mention page size limits or explicitly differentiate from google-maps.search, but overall it is comprehensive for a search tool.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaningful cross-parameter constraints (sort_by/radius/keyword interactions) and clarifies how to use cursor, which the schema does not state. This elevates it above the baseline.

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 description starts with 'Search for places near a latitude and longitude,' which is a specific verb-resource-scope pairing. It clearly distinguishes from sibling tools like google-maps.search (likely text-based) by anchoring on the lat/lng requirement.

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 description explicitly lists required and optional parameters, provides a conditional rule ('When sort_by is Distance, omit radius and provide keyword or place_type'), and explains cursor-based pagination. However, it does not explicitly name an alternative tool for text-based searches, so it stops short of full when-to-use vs. when-not-to-use guidance.

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

All Vee3 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.