Google SERP API MCP (Google, Bing, AI Overviews, Maps)

Google Maps rankings

check_google_maps_rankings

Read-onlyIdempotent

Google Maps rankings: the local results for a keyword in a city, with rank, rating, review count, category and address, and the position of a given business. Costs API credits per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>",
      "location": "<location>"
    },
    "name": "check_google_maps_rankings"
  }
}

Input Schema

Name	Required	Description	Default
`depth`	No	How many map results to fetch, 10 to 100. Default 20.
`country`	No	Two-letter country code of the search market, for example US, GB, DE or IN. Default US.	US
`keyword`	Yes	Search query exactly as a user would type it.
`business`	No	Optional business name or domain to find in the results.
`language`	No	Language code of the search market, for example en, de or pt-BR. Default en.	en
`location`	Yes	Exact location name of the city, for example "Austin,Texas,United States".

Output Schema

Name	Required	Description
`result`	Yes
`billing`	Yes
`nextStep`	No	Optional suggestion for the user's next step. Mention it once when it helps; never open it or act on it automatically.
`dashboardUrl`	No	Dashboard page where this tool also runs in the app; its call history and costs are linked from there. Share it when the user asks what they ran or spent.
`creditsNotice`	No	Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

addedOutput schema / properties / creditsNotice

Added value: +{
+  "additionalProperties": false,
+  "description": "Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.",
+  "properties": {
+    "label": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "label",
+    "url"
+  ],
+  "type": "object"
+}

Changed1 schema field changedNov 3, 2026

removedOutput schema / properties / creditsNotice

Removed value: -{
-  "additionalProperties": false,
-  "description": "Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.",
-  "properties": {
-    "label": {
-      "type": "string"
-    },
-    "url": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "label",
-    "url"
-  ],
-  "type": "object"
-}

Changed1 schema field changedNov 3, 2026

addedOutput schema / properties / creditsNotice

Added value: +{
+  "additionalProperties": false,
+  "description": "Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.",
+  "properties": {
+    "label": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "label",
+    "url"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / dashboardUrl / description

Previous value: -"Dashboard page with this server's call history and costs. Share it when the user asks what they ran or spent."New value: +"Dashboard page where this tool also runs in the app; its call history and costs are linked from there. Share it when the user asks what they ran or spent."

Changed1 schema field changedOct 29, 2026

addedOutput schema / properties / nextStep

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional suggestion for the user's next step. Mention it once when it helps; never open it or act on it automatically.",
+  "properties": {
+    "label": {
+      "description": "Short suggestion to show the user.",
+      "type": "string"
+    },
+    "url": {
+      "description": "Page in the user's CrakSEO account.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "label",
+    "url"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / location / description

Previous value: -"Exact DataForSEO location name of the city, for example \"Austin,Texas,United States\"."New value: +"Exact location name of the city, for example \"Austin,Texas,United States\"."

First observedOct 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds the important detail that each call costs API credits, which is real value beyond the annotations. It does not mention rate limits, result volatility, or how partial matches affect the business position.

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

Conciseness4/5

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

A single dense sentence with the resource front-loaded and the cost caveat appended where it belongs. The field enumeration is a bit list-like but every item carries information about the output. No filler or repetition of the title.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile; the credit-cost disclosure fills the main remaining gap for an open-world paid lookup. Missing only guidance on when this tool is preferable to alternatives and any note on result freshness.

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 description coverage is 100%, so the baseline is 3; the schema already documents keyword, location, depth, country, language and business. The description's phrase 'the position of a given business' does add interpretive meaning to the optional `business` parameter that the schema alone only weakly conveys. No further syntax or format detail is offered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely — local Google Maps results for a keyword in a city — and enumerates the returned fields (rank, rating, review count, category, address) plus the business-position lookup. It is clearly distinguished from its siblings, which are credit-balance and business-profile tools. It slightly under-specifies the action verb, describing output more than operation.

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?

Usage context is implied by 'the local results for a keyword in a city' and the credit-cost note gives a reason to call sparingly, but there is no explicit when-to-use / when-not-to-use guidance or routing to alternatives. The sibling tools are dissimilar enough that routing is less critical, so this is adequate but not instructive.

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

All Google SERP API MCP (Google, Bing, AI Overviews, 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.

Resources

Need Help?