Google Search Console MCP + Bing Webmaster Tools

Bing Webmaster Tools stats

get_bing_webmaster_stats

Read-onlyIdempotent

Bing Webmaster stats: Bing search queries, pages, or daily traffic for a site, with impressions, clicks and average positions. Bing also powers DuckDuckGo results. Free.

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": {
      "siteUrl": "<siteUrl>"
    },
    "name": "get_bing_webmaster_stats"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Most rows to return, 1 to 500. Default 100.
`report`	No	queries (per search query), pages (per page) or traffic (per day). Default queries.	queries
`siteUrl`	Yes	Site URL exactly as registered in Bing Webmaster Tools, for example https://example.com/.

Output Schema

Name	Required	Description
`rows`	Yes
`report`	Yes
`siteUrl`	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.

Schema Changelog

Changes observed during successful MCP inspections.

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"
+}

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 readOnlyHint, idempotentHint and destructiveHint=false, so safety is fully covered. The description adds a small amount of non-obvious behavioral context — coverage of DuckDuckGo results — but says nothing about authentication, account/site prerequisites, or data freshness/latency, which matter for a stats tool.

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 short sentences, front-loaded with the resource and report modes; nothing is buried. The fragment 'Free.' is slightly clipped but still informative rather than filler.

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 present, the description need not explain return values, and it does state the metrics delivered. What's missing is prerequisite context (site must already be registered in Bing Webmaster Tools, needs auth), which the schema only partially covers via the siteUrl description.

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 an enum on report and a bounded limit, so the schema carries parameter meaning fully. The description echoes the report options and metrics but adds no syntax or format detail beyond what the schema states; baseline 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?

The description names a specific resource (Bing Webmaster stats) and enumerates the report shapes (queries, pages, daily traffic) plus returned metrics (impressions, clicks, average positions). The 'Bing' qualifier implicitly separates it from the Google sibling (get_search_console_performance), though it never names that sibling 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?

Usage is implied by the metric list, and 'Bing also powers DuckDuckGo results. Free.' hints at why an agent might add this alongside Google data. But there is no explicit when-to-use / when-not guidance and no reference to any of the sibling tools that cover overlapping search-performance data.

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

All Google Search Console MCP + Bing Webmaster Tools 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?