SEO GSC Wizard MCP

Bing query + page pairs

get_bing_query_page_stats

Read-only

Use this when the user asks which Bing queries drive which of their pages. Bing Webmaster Tools query+landing-page pairs for a property, aggregated across the window (clicks, impressions, CTR as a 0-100 percentage, over 100 if Bing logs more clicks than impressions, and impression-weighted average position per pair): the basis for per-page keyword analysis and cannibalisation checks. Bing has no endpoint that returns these combinations, so they are assembled with one request per top page; pass query to pair from a single query instead, or use get_bing_page_queries for one page's queries. Coverage is bounded by seedLimit and by Bing's own top-value sampling, so totals are a lower bound (truncated says when). Bing dates the rows by week, so a window selects whole weeks by date. Not for Google cannibalisation: use analyze_cannibalization. Pairs are sorted by clicks, then impressions, highest first. Returns notConfigured: true when no Bing Webmaster API key is set up for the property.

Input Schema

Name	Required	Description
`limit`	No	Max query/page pairs, ranked by clicks then impressions (default 100, uncapped).
`query`	No	Optional. Pair from this single search query (Bing lists the pages that ranked for it) instead of fanning out over the top pages. Use it to answer "which pages compete for this term?".
`endDate`	No	Optional. Window end as YYYY-MM-DD (e.g. 2026-05-31). Omit BOTH startDate and endDate to return everything Bing has (about 16 months of search data, 6 of crawl data). Never pass null or the string "null".
`siteUrl`	Yes
`seedLimit`	No	How many top pages to expand into pairs (default 25, max 100). Each one is a separate Bing request, so raising it widens coverage but is slower and likelier to hit Bing rate limits. Only applies to the page fan-out, so a call that passes `query` uses it only if that path has to fall back to pairing by page.
`startDate`	No	Optional. Window start as YYYY-MM-DD (e.g. 2026-01-01). Omit BOTH startDate and endDate to return everything Bing has (about 16 months of search data, 6 of crawl data). Never pass null or the string "null".

Output Schema

Name	Required	Description
`hint`	No
`notes`	No
`pairs`	No
`range`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`siteUrl`	No
`warning`	No
`nextStep`	No
`ordering`	No
`pairedBy`	No
`rowCount`	No
`sortedBy`	No
`dateBasis`	No
`seedCount`	No
`sortOrder`	No
`thenOrder`	No
`truncated`	No
`dataSource`	No
`bingSiteUrl`	No
`partialDays`	No	Requested days among Bing's newest (provisional) or after latestDataDate (missing, not zero), up to today.
`completeness`	No
`emptyBecause`	No
`methodLimits`	No
`notConfigured`	No
`latestDataDate`	No	Newest date with a row in everything Bing sent for this call, before the window filter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 28, 2026

addedOutput schema / properties / completeness

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / dateBasis

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / latestDataDate

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Newest date with a row in everything Bing sent for this call, before the window filter."
+}

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Name of the top-level field that holds the rows sortedBy describes."
+}

addedOutput schema / properties / notes / $ref
```
Added value: +"#/properties/partialDays"
```

removedOutput schema / properties / notes / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / partialDays

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Requested days among Bing's newest (provisional) or after latestDataDate (missing, not zero), up to today."
+}

addedOutput schema / properties / warning

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

Changed13 schema fields changedOct 18, 2026

changedInput schema / properties / endDate / description

Previous value: -"Optional. Window end as YYYY-MM-DD (e.g. 2026-05-31). Omit BOTH startDate and endDate to return everything Bing has (roughly the last 6 months). Never pass null or the string \"null\"."New value: +"Optional. Window end as YYYY-MM-DD (e.g. 2026-05-31). Omit BOTH startDate and endDate to return everything Bing has (about 16 months of search data, 6 of crawl data). Never pass null or the string \"null\"."

changedInput schema / properties / startDate / description

Previous value: -"Optional. Window start as YYYY-MM-DD (e.g. 2026-01-01). Omit BOTH startDate and endDate to return everything Bing has (roughly the last 6 months). Never pass null or the string \"null\"."New value: +"Optional. Window start as YYYY-MM-DD (e.g. 2026-01-01). Omit BOTH startDate and endDate to return everything Bing has (about 16 months of search data, 6 of crawl data). Never pass null or the string \"null\"."

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / emptyBecause

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / methodLimits

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / nextStep

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / ordering

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "sortOrder": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "sortedBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenOrder": {
+            "$ref": "#/properties/siteUrl"
+          }
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / pairs / items / additionalProperties
```
Previous value: -falseNew value: +true
```

changedOutput schema / properties / range / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "days": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "endDate": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "startDate": {
-        "$ref": "#/properties/siteUrl"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "days": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "endDate": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "startDate": {
+        "$ref": "#/properties/siteUrl"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / sortOrder

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / sortedBy

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / thenBy

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / thenOrder

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

First observedOct 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Well beyond the annotations (readOnly/openWorld/non-destructive are already declared): it discloses that Bing has no endpoint for these combinations, that they are assembled with one request per top page (rate-limit implications), that coverage is a lower bound bounded by seedLimit and Bing's own sampling with a `truncated` flag, and that rows are dated by week. The only missing piece is a note on latency/cost of raising seedLimit beyond the schema's own text.

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?

Front-loaded with the trigger phrase, and each sentence carries distinct information (aggregation, fan-out mechanics, coverage bounds, weekly dating, sort order, notConfigured). It is a single dense paragraph, though, and the parenthetical of metrics plus the coverage caveats make it slower to scan than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values needn't be spelled out, yet the description still flags the notConfigured: true case an agent must handle. Combined with the fan-out cost model, truncation caveat, weekly date semantics and sort order, an agent has everything needed to call and interpret this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 83% schema coverage the baseline is 3, and the description earns above that by explaining the `query` shortcut (pair from a single query instead of fanning out) and the interaction where seedLimit only applies to the page fan-out or a fallback path. This meaning is partly duplicated in the schema property descriptions, but the description makes the query/seedLimit tradeoff explicit in one place.

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

Purpose5/5

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

States a specific verb and resource: Bing Webmaster Tools query+landing-page pairs for a property, aggregated over a window with clicks, impressions, CTR and impression-weighted position. It explicitly differentiates itself from siblings by naming get_bing_page_queries and analyze_cannibalization as the tools for adjacent questions.

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

Usage Guidelines5/5

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

Opens with an explicit trigger ('Use this when the user asks which Bing queries drive which of their pages') and gives three alternatives with the conditions that select them: pass `query` for a single query, use get_bing_page_queries for one page, use analyze_cannibalization for Google. When-to-use and when-not-to-use are both covered.

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

All SEO GSC Wizard MCP 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?