Local SEO Data

Official

Overview Schema Source Related Servers Discussions(1)Admin

keywords_for_site

Read-only

Discover which keywords a competitor domain ranks for and return search volume, CPC, and competition data for country-level keyword research.

Instructions

Use when reverse-engineering what keywords a competitor domain ranks for. Returns keywords with search_volume, cpc, and competition. IMPORTANT: volumes are country-level (volume_scope: "country") — our keyword database for this tool has no city/state granularity; check location_used for the actual scope. Costs 20 credits.

Input Schema

Name	Required	Description
`limit`	No	Max results. Default: 50, max: 1000
`domain`	Yes	Domain to analyze (e.g. "example.com")
`language`	No	Language as ISO 639-1 code or name (e.g. "fr", "fr-FR", "French"). Defaults to English wherever we hold an English database for that country, and to the largest database that country has otherwise.
`location`	Yes	Geographic location (e.g. "Orchard Park, NY")

Output Schema

Name	Required	Description	Default
`domain`	Yes
`keywords`	Yes
`language`	No
`location`	Yes
`data_source`	No
`total_count`	Yes
`volume_scope`	No
`location_used`	No
`location_alternatives`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.0Oct 22, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "Language as ISO 639-1 code or name (e.g. \"fr\", \"fr-FR\", \"French\"). Defaults to English wherever we hold an English database for that country, and to the largest database that country has otherwise.",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "data_source": {
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "keywords": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "competition": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "cpc": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "keyword": {
+            "type": "string"
+          },
+          "search_volume": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "keyword",
+          "search_volume",
+          "cpc",
+          "competition"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "language": {
+      "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"
+    },
+    "total_count": {
+      "type": "number"
+    },
+    "volume_scope": {
+      "enum": [
+        "local",
+        "country"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "keywords",
+    "total_count",
+    "domain",
+    "location"
+  ],
+  "type": "object"
+}

First observedv0.1.0May 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark it as read-only, non-destructive, and open-world. The description adds valuable behavior not in annotations: the 20-credit cost and the important caveat that volume data is country-level only, with location_used indicating actual scope.

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 three sentences, front-loads the use case, lists return fields, and clearly flags the critical volume-scope caveat and cost. Every sentence carries operational value.

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 that annotations cover safety, the schema documents all parameters, and an output schema exists, the description supplies the remaining operational essentials: return metrics, cost, and the country-level volume limitation. Nothing material appears missing for correct invocation.

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 the baseline is 3. The description adds meaningful semantic context about the location parameter's limitation: volumes are country-level and location_used should be checked for actual scope, which is more than the schema states.

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 states a specific verb and resource: reverse-engineering what keywords a competitor domain ranks for, and names the returned metrics. This clearly distinguishes it from generic keyword suggestion or search-volume tools in the sibling list.

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?

It gives an explicit usage context: 'Use when reverse-engineering what keywords a competitor domain ranks for.' However, it does not name alternatives such as keyword_opportunities or keyword_overview or state when not to use it.

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