Local SEO Data

Official

Overview Schema Source Related Servers Discussions(1)Admin

business_profile

Read-only

Retrieve a business's complete Google Business Profile data—address, phone, hours, categories, rating, reviews, photos, and verified status—by name and location. Includes Google Maps suggestions with place_id when no exact match is found.

Instructions

Use when pulling one business's complete GBP data. Returns name, address, phone, website, hours, categories, photos_count, rating, reviews_count, description, attributes, cid, place_id, and verified status. If no exact match is found, returns matched=false with up to 5 suggestions from Google Maps including place_id for exact retry. Costs 5 credits.

Input Schema

Name	Required	Description
`location`	Yes	City and state
`place_id`	No	Google Place ID for exact match
`business_name`	Yes	Business name

Output Schema

Name	Required	Description	Default
`cid`	Yes
`name`	Yes
`hours`	No
`phone`	Yes
`rating`	Yes
`address`	Yes
`matched`	No
`website`	Yes
`place_id`	Yes
`verified`	Yes
`attributes`	Yes
`categories`	Yes
`description`	Yes
`suggestions`	No
`photos_count`	Yes
`reviews_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.0Oct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "attributes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "categories": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "cid": {
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "hours": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "matched": {
+      "type": "boolean"
+    },
+    "name": {
+      "type": "string"
+    },
+    "phone": {
+      "type": "string"
+    },
+    "photos_count": {
+      "type": "number"
+    },
+    "place_id": {
+      "type": "string"
+    },
+    "rating": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "reviews_count": {
+      "type": "number"
+    },
+    "suggestions": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "address": {
+                "type": "string"
+              },
+              "categories": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "name": {
+                "type": "string"
+              },
+              "phone": {
+                "type": "string"
+              },
+              "place_id": {
+                "type": "string"
+              },
+              "rating": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "reviews_count": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "name",
+              "address",
+              "rating",
+              "reviews_count",
+              "place_id",
+              "phone",
+              "categories"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "verified": {
+      "type": "boolean"
+    },
+    "website": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "address",
+    "phone",
+    "website",
+    "categories",
+    "photos_count",
+    "rating",
+    "reviews_count",
+    "description",
+    "attributes",
+    "cid",
+    "place_id",
+    "verified"
+  ],
+  "type": "object"
+}

First observedv0.1.0May 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only and open-world behavior, and the description adds real operational context the annotations cannot: a 5-credit cost and a defined no-match path (matched=false plus up to 5 Maps suggestions with place_id for retry). It doesn't mention rate limits or auth, but it adds substantive behavior beyond structured fields.

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?

Four tight sentences, front-loaded with the use case and followed by payload, fallback, and cost. Every sentence carries information an agent would otherwise have to guess.

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?

Covers the use case, the fallback behavior, and the credit cost; an output schema exists so the field list is supplementary. Only gap is that the field enumeration duplicates the output schema, but nothing an agent needs for correct invocation 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 coverage is 100%, so business_name, location and place_id are already documented. The description's 'place_id for exact retry' reinforces but does not meaningfully extend the schema's own 'Google Place ID for exact match', so 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?

States a specific verb and scope: 'pulling one business's complete GBP data', plus an explicit field inventory. 'GBP' plus the Google Maps fallback makes it distinguishable from the apple_business_profile and bing_business_profile siblings without opening a 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?

'Use when pulling one business's complete GBP data' gives a clear selection condition, and the single-business scope implies it is not the tool for multi-record listing work. It does not name an alternative or exclusion explicitly (e.g. business_listings for bulk), so it stops short of a 5.

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