Local SEO Data

Official

Overview Schema Source Related Servers Discussions(1)Admin

business_listings

Read-only

Discover and collect all businesses in a category and location for bulk local listing data, including ratings, reviews, contact details, place IDs, coordinates, and categories within a search radius.

Instructions

Use when discovering all businesses in a category and location (bulk discovery, not single business lookup). Returns name, rating, reviews_count, address, city, phone, website, place_id, lat/lng, and categories for each, searched within search_radius_km of the location (location_used echoes where). Costs 10 credits per 50 results.

Input Schema

Name	Required	Description
`limit`	No	Number of results (1-200). Default: 50
`category`	Yes	Business category (e.g. "plumber", "dentist")
`location`	Yes	City and state

Output Schema

Name	Required	Description	Default
`category`	No
`location`	No
`businesses`	Yes
`location_used`	No
`total_available`	Yes
`search_radius_km`	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": {
+    "businesses": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "address": {
+            "type": "string"
+          },
+          "categories": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "cid": {
+            "type": "string"
+          },
+          "city": {
+            "type": "string"
+          },
+          "latitude": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "longitude": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "phone": {
+            "type": "string"
+          },
+          "place_id": {
+            "type": "string"
+          },
+          "rating": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "reviews_count": {
+            "type": "number"
+          },
+          "website": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "rating",
+          "reviews_count",
+          "address",
+          "phone",
+          "place_id",
+          "categories"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "category": {
+      "type": "string"
+    },
+    "location": {
+      "type": "string"
+    },
+    "location_used": {
+      "type": "string"
+    },
+    "search_radius_km": {
+      "type": "number"
+    },
+    "total_available": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "businesses",
+    "total_available"
+  ],
+  "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 declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, and the description adds real value beyond that: the credit cost model ('10 credits per 50 results'), the radius semantics, and the location_used echo. Minor deduction for referencing search_radius_km and location_used, which are not present in the input schema, which could make an agent search for a parameter it cannot set.

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?

A single front-loaded sentence opening with the usage trigger, followed by return fields, scoping behaviour and pricing. Every clause adds information an agent needs; nothing is redundant filler.

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?

Pricing, radius scoping and result-set composition make this callable without follow-up questions, and an output schema exists so return values need not be enumerated. However the description enumerates return fields that the output schema already covers, and the phantom radius/location_used references slightly muddy the parameter picture.

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 both required parameters are already documented, establishing a baseline of 3. The description adds meaning about radius behaviour and an echoed location field outside the schema, but says nothing about the limit parameter or how it interacts with the per-50-results cost, so it does not materially enrich parameter semantics.

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 resource ('discovering all businesses in a category and location') and immediately scopes it against the wrong interpretation ('bulk discovery, not single business lookup'). An agent can distinguish this from a single-business lookup or profile tool 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 ('Use when discovering all businesses in a category and location') plus one negative case (not single business lookup). It stops short of naming a specific sibling alternative such as local_finder or maps for overlapping discovery needs, so routing between near-duplicates is left partly to inference.

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