Bing Webmaster Tools MCP Server

get_children_url_info

Retrieve child URL details for any parent URL to analyze site structure and monitor indexing, with filtering and pagination for comprehensive results.

Instructions

Retrieve information for child URLs of a specific URL.

Args: site_url: The URL of the site url: The parent URL to get child URL information for page: The page number of results to retrieve filter_properties: Properties to filter the results

Returns: List[UrlInfo]: List of URL information for child URLs

Raises: BingWebmasterError: If child URL 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
`filter_properties`	No

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": {
+    "UrlInfo": {
+      "properties": {
+        "AnchorCount": {
+          "title": "Anchorcount",
+          "type": "integer"
+        },
+        "DiscoveryDate": {
+          "format": "date-time",
+          "title": "Discoverydate",
+          "type": "string"
+        },
+        "DocumentSize": {
+          "title": "Documentsize",
+          "type": "integer"
+        },
+        "HttpStatus": {
+          "title": "Httpstatus",
+          "type": "integer"
+        },
+        "IsPage": {
+          "title": "Ispage",
+          "type": "boolean"
+        },
+        "LastCrawledDate": {
+          "format": "date-time",
+          "title": "Lastcrawleddate",
+          "type": "string"
+        },
+        "TotalChildUrlCount": {
+          "title": "Totalchildurlcount",
+          "type": "integer"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "AnchorCount",
+        "DiscoveryDate",
+        "DocumentSize",
+        "HttpStatus",
+        "IsPage",
+        "LastCrawledDate",
+        "TotalChildUrlCount",
+        "Url"
+      ],
+      "title": "UrlInfo",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/UrlInfo"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_children_url_infoOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses pagination behavior ('Returns at most limit rows... call again with offset=next_offset') and error handling (BingWebmasterError). It does not mention auth, rate limits, or other side effects, but given this is a read operation, the disclosed behavior is sufficient for basic use. It adds value beyond the schema.

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-organized: a one-line purpose, a compact Args list, Returns and Raises sections, and a crucial pagination note. It is front-loaded and every sentence adds value. No redundancy or fluff.

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 6-parameter surface, a nested filter object, and an output schema, the description covers the essential purpose, parameter meanings, pagination, and error. The output schema defines return structure, and the filter details are in the schema. It only lacks usage-selection context, which is already scored under usage_guidelines, so for the tool's calling mechanics it is sufficiently complete.

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?

Schema description coverage is only 33% (limit and offset have descriptions). The description explicitly explains site_url, url, page, and filter_properties in an Args block, compensating for the undocumented parameters. It gives concise meanings for each, though filter_properties is only described at a high level without detailing the nested structure. This is valuable addition beyond the schema.

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 clear, specific verb+resource: 'Retrieve information for child URLs of a specific URL.' This differentiates it from siblings like get_url_info (single URL) and get_children_url_traffic_info (traffic-specific) by focusing on child URLs and general info. It does not explicitly name alternatives, but the purpose is unambiguous.

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_url_info or get_children_url_traffic_info. It only explains how to paginate once called, not the selection criteria for choosing this tool. This omission leaves the agent to infer from the name and siblings.

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

Deploy Server