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

Google AI Overview sources

get_ai_overview_sources

Read-onlyIdempotent

AI Overview sources: whether Google shows an AI Overview for a keyword, its text, every page it cites, and whether a given domain is cited. 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>"
    },
    "name": "get_ai_overview_sources"
  }
}

Input Schema

Name	Required	Description	Default
`device`	No	Device to emulate. Default desktop.	desktop
`domain`	No	Optional domain to check for a citation, for example example.com.
`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.
`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.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior beyond that: the per-call API credit cost and the fact that the response includes both the overview text and citation checks. It stops short of mentioning latency, quota, or failure modes when no overview exists.

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 sentence that front-loads the resource and enumerates the outputs, with the cost caveat appended rather than buried. No filler, no restatement of the title, and every clause carries information an agent would use.

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, return values need not be spelled out, and the description still summarizes them effectively. Combined with the credit-cost disclosure and full parameter documentation, an agent has what it needs to call the tool correctly; only cross-tool routing guidance is missing.

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%, with every parameter (device, country, language, location, domain, keyword) documented including defaults and formats, so the baseline is 3. The description mentions 'keyword' and 'a given domain' but adds no syntax, precedence, or market-targeting detail beyond what the schema already states, notably nothing about location overriding country.

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 a specific resource (Google AI Overview) and enumerates exactly what is returned: whether an overview exists, its text, its cited pages, and whether a given domain is cited. That is far more informative than the name alone. It doesn't explicitly contrast itself with the sibling check_chatgpt_brand_mentions / check_perplexity_brand_mentions tools, but the Google/overview framing makes the distinction inferable.

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 is implied: use it to learn if Google renders an AI Overview for a keyword and whether a domain is cited. There is no explicit when-to-use / when-not-to-use statement and no routing to the sibling brand-mention tools for non-Google engines. The cost warning ('Costs API credits per call') is a useful decision input but not usage guidance per se.

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?