Bing Webmaster Tools MCP Server

get_fetched_urls

Retrieve the list of URLs submitted for fetching, including their status, with support for pagination to handle large result sets.

Instructions

Get a list of URLs that have been submitted for fetching.

Args: site_url: The URL of the site

Returns: List[FetchedUrl]: List of fetched URLs and their status

Raises: BingWebmasterError: If fetched URLs 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": {
+    "FetchedUrl": {
+      "properties": {
+        "Date": {
+          "format": "date-time",
+          "title": "Date",
+          "type": "string"
+        },
+        "Expired": {
+          "title": "Expired",
+          "type": "boolean"
+        },
+        "Fetched": {
+          "title": "Fetched",
+          "type": "boolean"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Date",
+        "Expired",
+        "Fetched",
+        "Url"
+      ],
+      "title": "FetchedUrl",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/FetchedUrl"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_fetched_urlsOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

A3.7/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 full behavioral burden. It discloses the pagination contract (limit, max, next_offset), the return type with status, and a Raises clause for error conditions. It does not explicitly state read-only behavior, but the verb 'Get' makes non-mutation reasonably clear.

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 a one-sentence purpose, compact Args/Returns/Raises sections, and a crucial pagination note. The Args section redundantly lists only one of three parameters, which is a minor inconsistency, but overall every element earns its place with no 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?

The output schema covers return-value structure, and the description covers pagination and error behavior, so agents have what they need to invoke and iterate. The main gaps are that it doesn't mention that site_url must be a verified site or explicitly route users to get_fetched_url_details for single-URL details.

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 coverage is 67%; limit and offset already have clear schema descriptions, so the description adds little there. For site_url, it only says 'The URL of the site,' which is minimally more than the schema's title. The next_offset/offset interplay is behavioral guidance rather than new parameter semantics.

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 starts with a clear verb-resource pair: 'Get a list of URLs that have been submitted for fetching.' This is specific enough to convey the tool's core function. It doesn't explicitly name or distinguish from the sibling get_fetched_url_details, but 'list' versus 'details' creates reasonable separation.

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 provides concrete usage guidance for pagination: 'call again with offset=next_offset to get more rows.' However, it does not state when to choose this tool over alternatives like get_fetched_url_details or submit_url, leaving the selection context implied rather than explicit.

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

Deploy Server