SEO GSC Wizard MCP

Bing daily traffic

get_bing_traffic_stats

Read-only

Use this when the user asks how much traffic Bing sends their site over time. Daily clicks and impressions from Bing Webmaster Tools (Bing/Yahoo/DuckDuckGo organic) for a property, up to about 16 months, plus window totals. Complements Google Search Console data with the Bing side of organic search. Not for Google traffic: use get_site_summary. Rows are sorted by date, oldest first. Returns notConfigured: true when no Bing Webmaster API key is set up for the property.

Input Schema

Name	Required	Description
`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
`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
`daily`	No
`range`	No
`thenBy`	No
`totals`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`siteUrl`	No
`warning`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`dateBasis`	No
`sortOrder`	No
`thenOrder`	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.

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

Changed14 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
```
changedOutput schema / properties / daily / items / 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 / 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"
+}

changedOutput schema / properties / totals / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "clicks": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      },
-      "impressions": {
-        "$ref": "#/properties/range/anyOf/0/properties/days"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "clicks": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      },
+      "impressions": {
+        "$ref": "#/properties/range/anyOf/0/properties/days"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare a read-only, non-destructive, open-world read, so the safety profile is covered; the description adds real behavioral value on top: the ~16-month data horizon, oldest-first date sorting, window totals, and the notConfigured: true state when no Bing API key exists. It doesn't discuss pagination or rate limiting, but the special return state is exactly the kind of operational detail annotations cannot express.

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 use case, then scope, then exclusions, then output behavior — a sensible order with no filler. The GSC-complement sentence is mildly redundant with the preceding one, keeping it just short of a 5.

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?

An output schema exists, so return values need no prose, and the description still flags the notable notConfigured case and sort order. Parameters and the required siteUrl are handled by the schema, so an agent has what it needs to call this correctly; only minor detail (multiple properties, date semantics) is left to schema inference.

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 67%, and the two optional date parameters already have thorough schema descriptions (format, omit-both-for-everything, 16-month limit). The description only alludes to a 'window' and 16-month horizon; it never explains startDate/endDate behavior or the required siteUrl. With the schema doing most of the work, this lands at the baseline 3 rather than higher.

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 (get daily Bing traffic stats) and pins the scope precisely: daily clicks and impressions from Bing Webmaster Tools for a property, up to ~16 months, plus window totals. It explicitly names the sibling it is not (get_site_summary for Google traffic) and positions itself relative to Google Search Console, so an agent can distinguish it from the many other bing_* tools without opening the 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?

The opening sentence gives the exact triggering question ('how much traffic Bing sends their site over time'), and 'Not for Google traffic: use get_site_summary' supplies an explicit exclusion plus the correct alternative. That covers when-to-use, when-not, and the redirect target in two sentences.

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?