Local SEO Data

Official

Overview Schema Source Related Servers Discussions(1)Admin

local_pack

Read-only

Check where businesses rank in Google's local pack for a keyword and retrieve rank, rating, reviews, address, phone, hours, and website; adjust depth or device for broader desktop or mobile results.

Instructions

Checks where businesses rank in Google's local pack for a keyword. Returns rank, name, cid, rating, reviews_count, address, phone, hours, website. Returns the top 3 by default; set depth for a deeper local ranking list (up to 60), and device to check desktop vs mobile. maps returns GPS coordinates and place_ids instead of CIDs. Costs 2 credits.

Input Schema

Name	Required	Description
`depth`	No	Number of results. Default: 20, max: 60
`device`	No	Device type. Default: desktop
`keyword`	Yes	Search keyword (e.g. "plumber")
`location`	Yes	City and state (e.g. "Orchard Park, NY")

Output Schema

Name	Required	Description	Default
`keyword`	Yes
`results`	Yes
`location`	Yes
`location_used`	No
`total_results`	Yes
`location_alternatives`	No

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": {
+    "keyword": {
+      "type": "string"
+    },
+    "location": {
+      "type": "string"
+    },
+    "location_alternatives": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "code": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "code",
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "location_used": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "address": {
+            "type": "string"
+          },
+          "cid": {
+            "type": "string"
+          },
+          "hours": {},
+          "name": {
+            "type": "string"
+          },
+          "phone": {
+            "type": "string"
+          },
+          "rank": {
+            "type": "number"
+          },
+          "rating": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "reviews_count": {
+            "type": "number"
+          },
+          "website": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "rank",
+          "name",
+          "cid",
+          "rating",
+          "reviews_count",
+          "address",
+          "phone",
+          "website"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_results": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "results",
+    "total_results",
+    "keyword",
+    "location"
+  ],
+  "type": "object"
+}

First observedv0.1.0May 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, open-world, non-destructive operation. The description adds useful behavior beyond annotations: it states the credit cost, describes the returned fields, and explains depth and device effects. The only issue is that its stated default result count conflicts with the schema's default.

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?

The description is front-loaded with the core purpose and then efficiently covers output fields, depth, device, the `maps` distinction, and cost. It is appropriately sized and has no wasted sentences.

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

Completeness3/5

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

An output schema exists, and annotations cover the safety profile, so the description does not need to carry the full burden. It is still mostly complete, but the incorrect default-result statement conflicts with the schema and leaves an agent unsure about how many results will be returned without setting depth.

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 the schema already documents keyword, location, depth, and device. The description adds some semantic context for depth and device, but it says the tool returns the top 3 by default while the schema says depth defaults to 20, creating a meaningful ambiguity.

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 names a specific verb and resource: checking where businesses rank in Google's local pack for a keyword. It also distinguishes the tool from the sibling `maps` tool by explaining that `maps` returns GPS coordinates and place_ids instead of CIDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the use case is local-pack rank checking and explicitly contrasts with `maps` for a different output shape. However, it does not say when to use this instead of other local or keyword tools such as `local_finder`, `organic_serp`, or `business_profile`.

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