Google_maps

Maps Place Details

maps_place_details

Read-onlyIdempotent

"Hours / phone / reviews of [business]" / "Google business info for [place]" / "is [restaurant] open" — full details for a Google Place: address, phone, hours, website, ratings, user reviews. Requires a place ID from maps_place_search. Use after search to drill into one specific business.

Input Schema

Name	Required	Description	Default
`_apiKey`	Yes	Google Maps API key
`place_id`	Yes	Google Place ID

Output Schema

Name	Required	Description	Default
`result`	No	Detailed place information
`status`	No	Status of the place details request

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "description": "Detailed place information",
+      "properties": {
+        "formatted_address": {
+          "description": "Formatted address",
+          "type": "string"
+        },
+        "formatted_phone_number": {
+          "description": "Place phone number",
+          "type": "string"
+        },
+        "geometry": {
+          "description": "Location geometry",
+          "properties": {
+            "location": {
+              "properties": {
+                "lat": {
+                  "description": "Latitude",
+                  "type": "number"
+                },
+                "lng": {
+                  "description": "Longitude",
+                  "type": "number"
+                }
+              },
+              "type": "object"
+            }
+          },
+          "type": "object"
+        },
+        "name": {
+          "description": "Place name",
+          "type": "string"
+        },
+        "opening_hours": {
+          "description": "Operating hours information",
+          "properties": {
+            "open_now": {
+              "description": "Whether currently open",
+              "type": "boolean"
+            },
+            "periods": {
+              "description": "Weekly operating periods",
+              "type": "array"
+            },
+            "weekday_text": {
+              "description": "Human-readable weekly hours",
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            }
+          },
+          "type": "object"
+        },
+        "place_id": {
+          "description": "Unique Google place ID",
+          "type": "string"
+        },
+        "price_level": {
+          "description": "Price level (1-4, where 4 is most expensive)",
+          "type": "integer"
+        },
+        "rating": {
+          "description": "Average user rating (0-5)",
+          "type": "number"
+        },
+        "reviews": {
+          "description": "User reviews",
+          "items": {
+            "properties": {
+              "author_name": {
+                "description": "Reviewer name",
+                "type": "string"
+              },
+              "rating": {
+                "description": "Review rating (1-5)",
+                "type": "number"
+              },
+              "text": {
+                "description": "Review text",
+                "type": "string"
+              },
+              "time": {
+                "description": "Review timestamp (Unix)",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "types": {
+          "description": "Place type categories",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "website": {
+          "description": "Place website URL",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "status": {
+      "description": "Status of the place details request",
+      "enum": [
+        "OK",
+        "ZERO_RESULTS",
+        "NOT_FOUND",
+        "INVALID_REQUEST",
+        "OVER_QUERY_LIMIT",
+        "REQUEST_DENIED",
+        "UNKNOWN_ERROR"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-google_maps-api-key",
+    "place_id": "ChIJIQBpAG2dQIcR_6128GltTXQ"
+  }
+]

First observedApr 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral context: returns full details (hours, phone, reviews, etc.) and relies on a prior search step, aiding agent understanding beyond the annotations.

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

Conciseness5/5

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

Two sentences with front-loaded example queries. Every word adds value, no fluff.

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?

Given the presence of an output schema, the description adequately covers the tool's inputs and outputs. It lists key return fields (address, phone, hours, etc.) and links to the required precursor tool.

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 coverage is 100% with descriptions for both parameters. The description reinforces that place_id comes from `maps_place_search` but adds no new semantic detail beyond the schema.

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 natural language queries like 'Hours / phone / reviews of [business]' and clearly states it provides full details for a Google Place: address, phone, hours, website, ratings, user reviews. It also distinguishes from sibling tool `maps_place_search` by specifying it requires a place ID from that search.

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?

Explicit guidance to 'Use after search to drill into one specific business' and requires a place ID from `maps_place_search`. While it doesn't mention when not to use, the context is clear enough.

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.