Bing Webmaster Tools MCP Server

get_query_stats

Retrieve detailed traffic statistics for top search queries on a site, with pagination support for large datasets. Use it to analyze which queries drive clicks and impressions.

Instructions

Get detailed traffic statistics for top queries.

Args: site_url: The URL of the site

Returns: List[QueryStats]: List of statistics for top queries

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.
`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"
-]New value: +[
+  "site_url"
+]

Changed1 schema field changedv1.0.0Jan 2, 2026

changedOutput schema / (root)

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

First observedApr 11, 2025

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does add useful behavior: pagination via next_offset/offset, a default and maximum limit, and error type. However, it does not describe data scope, permissions, or what 'top queries' specifically means.

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?

The description is well-structured with Args, Returns, and Raises sections, plus a concise pagination note. There is minimal redundancy; the only slight overlap is between the opening sentence and the Returns line. Overall, every sentence contributes.

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?

For a simple 3-parameter paginated query tool, the description covers the call pattern, return type, error raising, and pagination. The presence of an output schema likely covers return value details. It lacks tool-selection context and permission prerequisites, but is otherwise reasonably complete.

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?

The schema already documents limit and offset well. The description adds slightly to site_url by calling it 'The URL of the site' and explains how offset relates to next_offset. With 67% schema coverage, the description partially compensates but still does not clarify site_url format or constraints.

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 a specific action and resource: 'Get detailed traffic statistics for top queries.' This is unambiguous as a verb+resource statement, but it does not explicitly differentiate itself from similar siblings like get_query_traffic_stats or get_query_page_stats, so it loses a point.

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 use this tool versus alternatives such as get_query_traffic_stats or get_keyword_stats. It mentions how pagination works, but that is an invocation detail, not a selection criterion or context for choosing this tool.

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

Deploy Server