Bing Webmaster Tools MCP Server

get_children_url_traffic_info

Retrieve traffic details for child URLs under a directory. Use this to analyze performance of subpages and identify which URLs drive traffic.

Instructions

Get traffic details for child URLs of a directory.

Args: site_url: The URL of the site url: The URL of the directory page: The page number of results to retrieve

Returns: List[UrlTrafficInfo]: List of traffic information for child URLs

Raises: BingWebmasterError: If child traffic information 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
`url`	Yes
`page`	No
`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",
-  "url"
-]New value: +[
+  "site_url",
+  "url"
+]

Changed1 schema field changedv1.0.0Jan 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "UrlTrafficInfo": {
+      "properties": {
+        "Clicks": {
+          "title": "Clicks",
+          "type": "integer"
+        },
+        "Impressions": {
+          "title": "Impressions",
+          "type": "integer"
+        },
+        "IsPage": {
+          "title": "Ispage",
+          "type": "boolean"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Clicks",
+        "Impressions",
+        "IsPage",
+        "Url"
+      ],
+      "title": "UrlTrafficInfo",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/UrlTrafficInfo"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_children_url_traffic_infoOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description must carry the burden. It discloses pagination behavior (limit, offset, next_offset), return type, and error conditions (BingWebmasterError). It does not mention rate limits, authentication, or that it is read-only, but the core behavioral aspects are covered. The absence of annotation contradictions supports this score.

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 clear sections (Args, Returns, Raises) and front-loads the primary purpose. It includes necessary details about pagination and errors without excessive verbosity. The only minor redundancy is repeating 'Returns' twice, but overall it is efficient.

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 5-parameter tool with no annotations and an output schema (though not shown), the description covers purpose, all parameters, pagination, and error handling. It does not mention authentication or rate limits, but these may be implicit for the API. It is complete enough for an agent to invoke correctly, with minor gaps.

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

Parameters5/5

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

Schema coverage is only 40% (limit and offset have descriptions), but the description compensates fully. The Args section explains site_url, url, and page, while the later text explains limit and offset with defaults and max values. Every parameter is meaningfully described, adding significant value beyond the schema.

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?

The opening sentence clearly states the specific action ('Get traffic details') and resource ('child URLs of a directory'). This distinguishes it from sibling tools like get_url_traffic_info (single URL) and get_children_url_info (likely without traffic) by explicitly mentioning 'traffic'. The purpose is unambiguous and action-oriented.

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 explains pagination usage ('call again with offset=next_offset') but does not explicitly state when to use this tool versus alternatives such as get_url_traffic_info or get_children_url_info. It provides context that it is for a directory's children, but does not name alternatives or exclusions. This is a clear gap for tool selection.

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

Deploy Server