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

Check Google rankings for a domain

check_google_rankings

Read-onlyIdempotent

Check Google rankings: the live Google position and ranking URL of a domain for up to 10 keywords in one country, with the top competing domains. Costs API credits per keyword.

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": {
      "domain": "<domain>",
      "keywords": "<keywords>"
    },
    "name": "check_google_rankings"
  }
}

Input Schema

Name	Required	Description	Default
`depth`	No	How deep to look for the domain, 10 to 100 results. Default 30.
`device`	No	Device to emulate. Default desktop.	desktop
`domain`	Yes	Domain or URL, for example example.com. Protocol and www are ignored.
`country`	No	Two-letter country code of the search market, for example US, GB, DE or IN. Default US.	US
`keywords`	Yes	Up to 10 keywords to check, one live Google search each.
`language`	No	Language code of the search market, for example en, de or pt-BR. Default en.	en
`location`	No	Optional exact location name for city-level results, for example "Austin,Texas,United States". Overrides country.

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: -"Optional exact DataForSEO location name for city-level results, for example \"Austin,Texas,United States\". Overrides country."New value: +"Optional exact location name for city-level results, for example \"Austin,Texas,United States\". Overrides country."

First observedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds genuinely new context: one live Google search per keyword and that each keyword consumes API credits, which an agent needs before invoking a metered call. It omits the actual credit cost per keyword or any rate limits.

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 front-loaded sentence with the key facts (what it returns, the scope limits, the cost) in descending order of importance. Dense but no filler; the colon-led structure makes the core action readable at a glance.

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?

An output schema exists, so return values do not need explaining, and annotations cover the safety profile. What remains missing is the relative positioning against get_ranked_keywords and any indication of how expensive the credit cost is, minor gaps for a 7-parameter read-only tool.

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%, including depth, device, country, language, and location, so the schema already carries the parameter meaning. The description only restates the keyword cap and single-country constraint, adding little beyond the schema.

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?

States a specific verb and resource (check live Google position and ranking URL of a domain) plus the scope limits (up to 10 keywords, one country, top competing domains). It is clearly distinct from sibling tools like find_competitor_domains or get_ranked_keywords, though it never names an alternative explicitly.

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?

The word 'live' implies this is for on-demand checks rather than stored/historical data, which is the main axis separating it from get_ranked_keywords, but the description never states when to prefer one over the other. No prerequisites, exclusions, or alternative routing are given.

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?