Bing Webmaster Tools MCP Server

get_query_traffic_stats

Retrieve detailed Bing Search traffic statistics for a specific query on a site, with pagination support for large result sets.

Instructions

Get detailed traffic statistics for a specific query.

Args: site_url: The URL of the site query: The search query to get statistics for

Returns: List[RankAndTrafficStats]: List of traffic statistics for the query

Raises: BingWebmasterError: If statistics cannot be retrieved

Returns at most limit rows (default 50, max 500). When the result reports a next_offset, call again with offset=next_offset to get more rows.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of rows to return.
`query`	Yes
`offset`	No	Index of the first row.
`site_url`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.0Sep 26, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 50,
+  "description": "Maximum number of rows to return.",
+  "maximum": 500,
+  "minimum": 1,
+  "title": "Limit",
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Index of the first row.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}

removedInput schema / properties / self

Removed value: -{
-  "title": "self",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "self",
-  "site_url",
-  "query"
-]New value: +[
+  "site_url",
+  "query"
+]

Changed1 schema field changedv1.0.0Jan 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "RankAndTrafficStats": {
+      "properties": {
+        "Clicks": {
+          "title": "Clicks",
+          "type": "integer"
+        },
+        "Date": {
+          "format": "date-time",
+          "title": "Date",
+          "type": "string"
+        },
+        "Impressions": {
+          "title": "Impressions",
+          "type": "integer"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Clicks",
+        "Date",
+        "Impressions"
+      ],
+      "title": "RankAndTrafficStats",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/RankAndTrafficStats"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_query_traffic_statsOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the return type, raises BingWebmasterError on failure, and explains limit/offset pagination semantics including the next_offset pattern. It does not mention rate limits or authentication, but for a read-only statistics tool the disclosed behavior is substantial.

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?

The description is well-structured and compact: a clear purpose sentence, an Args section, a Returns section, a Raises section, and a pagination note. Every sentence adds meaningful information without unnecessary verbosity.

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?

The description is largely complete for invoking the tool: required inputs, return type, error behavior, and pagination are all covered. An output schema exists, so return field details are not required. The main gap is the lack of explicit routing guidance among the many query-stats sibling tools.

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 only 50%, so the description must compensate. It provides minimal semantics for site_url and query ('URL of the site', 'search query'), and it adds useful pagination semantics for limit and offset via the next_offset explanation. However, the required parameters lack deeper format or usage detail.

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 clearly states the action and resource: 'Get detailed traffic statistics for a specific query.' It is specific about needing site_url and query. However, it does not explicitly differentiate itself from siblings like get_query_stats or get_rank_and_traffic_stats, which also appear relevant based on their names.

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?

The description provides no guidance on when to choose this tool over the many sibling tools, such as get_query_stats, get_query_page_stats, or get_rank_and_traffic_stats. It does explain pagination usage, but that is operational guidance rather than tool-selection guidance.

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

Deploy Server