Bing Webmaster Tools MCP Server

get_page_stats

Retrieve detailed traffic statistics for top pages of a site, revealing query-level performance and high-traffic URLs to inform SEO decisions.

Instructions

Get detailed traffic statistics for top pages.

Args: site_url: The URL of the site

Returns: List[QueryStats]: List of query statistics for top pages

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_page_statsOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses pagination behavior (limit, offset, next_offset) and the BingWebmasterError exception, which is useful. However, it does not mention potential rate limits, permission requirements, or any side effects, and it does not clarify what 'top pages' 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/Raises sections and a clear one-line purpose. It includes necessary pagination details without unnecessary elaboration, though the formatting is a bit formal.

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?

Given the tool's simplicity, an output schema, and three parameters, the description covers the essential usage: pagination, error handling, and parameter semantics. It is sufficient to call the tool correctly, though it could mention what constitutes 'top pages' or any prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema describes limit and offset, but the description adds meaning by explaining how offset works with next_offset for pagination and the default/max limits. It also provides a description for site_url, which is missing from the schema, thus compensating for the 67% coverage gap.

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 verb 'Get' and the resource 'detailed traffic statistics for top pages'. It is specific enough to distinguish from many sibling tools that focus on query-level or crawl stats, though it does not explicitly name alternatives.

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?

There is no guidance on when to use this tool versus alternatives such as get_query_stats or get_rank_and_traffic_stats. No conditions, exclusions, or alternative references are provided, leaving the selection entirely to the agent's inference.

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

Deploy Server