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

Bing SERP results

get_bing_serp

Read-onlyIdempotent

Bing SERP API: live Bing search results for any keyword and country, with organic positions, titles and URLs. Bing results also power DuckDuckGo and other engines. 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_bing_serp"
  }
}

Input Schema

Name	Required	Description	Default
`depth`	No	How many results to fetch, 10 to 100. Default 10.
`device`	No	Device to emulate. Default desktop.	desktop
`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

B3.2/5.0

Behavior3/5

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

The annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is well covered. The description adds the credit-consumption cost, which is genuinely useful context not present in structured fields, but stops short of saying whether cost scales with depth or how failures are billed.

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?

Two tight sentences that front-load the capability and end with the cost caveat. The aside about Bing powering DuckDuckGo is mildly relevant positioning but is the least load-bearing clause.

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 a full output schema, 100% parameter coverage and four annotation hints, the description need only carry purpose and cost, which it does. The remaining gap is the absence of engine-selection guidance among the SERP siblings.

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 every parameter (depth, device, country, language, location) is already fully documented with defaults, ranges and patterns. The description only echoes 'keyword and country', adding no semantics beyond the schema, so the baseline of 3 applies.

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?

Describes a specific verb and resource ('live Bing search results for any keyword and country') and names the return payload (organic positions, titles, URLs). It implicitly distinguishes itself from the get_google_serp sibling by naming the engine, but never states the distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not guidance, and no sibling is named as an alternative for Google-engine queries. The only consumption signal is 'costs API credits per call', which hints at a tradeoff but doesn't tell the agent when to pick this over get_google_serp.

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?