Bing Webmaster Tools MCP Server

get_query_page_detail_stats

Retrieve detailed stats for a specific query and page combination. Specify site URL, query, and page to get performance metrics.

Instructions

Get detailed statistics for a specific query and page combination.

Args: site_url: The URL of the site query: The search query page: The specific page URL

Returns: List[DetailedQueryStats]: List of detailed statistics

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
`page`	Yes
`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",
-  "page"
-]New value: +[
+  "site_url",
+  "query",
+  "page"
+]

Changed1 schema field changedv1.0.0Jan 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "DetailedQueryStats": {
+      "properties": {
+        "Clicks": {
+          "title": "Clicks",
+          "type": "integer"
+        },
+        "Date": {
+          "format": "date-time",
+          "title": "Date",
+          "type": "string"
+        },
+        "Impressions": {
+          "title": "Impressions",
+          "type": "integer"
+        },
+        "Position": {
+          "title": "Position",
+          "type": "integer"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Clicks",
+        "Date",
+        "Impressions",
+        "Position"
+      ],
+      "title": "DetailedQueryStats",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/DetailedQueryStats"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_query_page_detail_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 provided, the description carries the behavioral disclosure burden. It clearly explains the pagination loop with `limit`, `offset`, and `next_offset`, and documents that a `BingWebmasterError` can be raised. This adds useful behavioral context beyond the raw schema.

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 organized with Args, Returns, and Raises sections, and the pagination behavior is front-loaded after the initial purpose. It is a bit longer than strictly necessary but each sentence contributes meaningful operational detail.

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

Completeness3/5

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

The description covers the essential call patterns, pagination, and error behavior. With output schema present, return-field details are not required. However, given the large set of closely named statistics siblings, the definition would be stronger if it explained how this tool differs from `get_query_page_stats` or when to prefer one over the other.

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 40%, so the description must compensate. It clarifies that `page` is a page URL and explains the pagination behavior for `limit` and `offset`. However, `site_url` and `query` are only restated with minimal elaboration, so the gap is only partially filled.

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 states a specific verb and resource: 'Get detailed statistics for a specific query and page combination.' This clearly identifies what the tool does, though it does not explicitly distinguish it from the similar sibling tools like get_query_page_stats or get_page_query_stats.

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

Usage Guidelines3/5

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

The description implies the tool is for retrieving detailed stats for a specific query and page URL, but it gives no explicit guidance about when to choose this over the many similar query/page statistic tools in the sibling list. No exclusions or alternatives are named.

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

Deploy Server