SEO GSC Wizard MCP

Bing keyword impression history

get_bing_keyword_stats

Read-only

Use this when the user asks how much Bing search demand a keyword has, or how it moves with the seasons. Bing Webmaster Tools' historical impression volume for a single keyword (weekly buckets, oldest first), plus its broad-match impressions. This is Bing marketplace demand data, not tied to any of your properties, so it needs no siteUrl. Not for your site's Bing queries: use get_bing_query_stats. Returns notConfigured: true when no Bing Webmaster API key is set up in the GSC Wizard app.

Input Schema

Name	Required	Description	Default
`country`	No	Two-letter market/country code Bing scopes the demand to (default "us").	us
`keyword`	Yes	The keyword / search term to look up.
`language`	No	BCP-47 language tag for the market (default "en-US").	en-US

Output Schema

Name	Required	Description
`hint`	No
`count`	No
`stats`	No
`thenBy`	No
`country`	No
`keyword`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`warning`	No
`language`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`dateBasis`	No
`sortOrder`	No
`thenOrder`	No
`dataSource`	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.

Changed6 schema fields changedOct 28, 2026

addedOutput schema / properties / completeness

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

addedOutput schema / properties / dateBasis

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

addedOutput schema / properties / latestDataDate

Added value: +{
+  "$ref": "#/properties/keyword",
+  "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/keyword",
+  "description": "Name of the top-level field that holds the rows sortedBy describes."
+}

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

Changed10 schema fields changedOct 18, 2026

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

addedOutput schema / properties / emptyBecause

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

addedOutput schema / properties / methodLimits

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

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

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

First observedOct 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare read-only and open-world, but the description adds material context: weekly buckets ordered oldest-first, inclusion of broad-match impressions, that it is marketplace demand data requiring no siteUrl, and the notConfigured: true failure mode when no API key exists. That last item is an error behavior an agent could not infer from annotations.

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?

Four sentences, each doing distinct work: trigger, what it returns, scope clarification, sibling exclusion, and failure mode. The trigger and the sibling routing are front-loaded, and nothing is repeated from the schema.

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 shape needn't be explained, and the description still covers the non-obvious parts an agent needs: bucket granularity and ordering, broad-match inclusion, no siteUrl requirement, and the notConfigured precondition. Nothing needed to call it correctly 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 coverage is 100%, so country, language, and keyword are fully documented in the schema and the default values are visible. The description only adds the negative fact that no siteUrl is needed, which clarifies scope rather than parameter usage. Baseline 3 is appropriate.

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+resource ('historical impression volume for a single keyword') plus the analysis angle ('how it moves with the seasons'), and explicitly contrasts with the sibling get_bing_query_stats. An agent can route correctly without opening either schema.

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 how much Bing search demand a keyword has') and gives an explicit exclusion with the named alternative ('Not for your site's Bing queries: use get_bing_query_stats'). Covers both when and when-not.

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?