Bing Webmaster Tools MCP Server

get_blocked_urls

Retrieve blocked URLs and directories for a site, with pagination support. Use to audit and manage blocked content.

Instructions

Get a list of blocked pages/directories for a site.

Args: site_url: The URL of the site

Returns: List[BlockedUrl]: List of blocked URLs and their settings

Raises: BingWebmasterError: If blocked 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": {
+    "BlockedUrl": {
+      "properties": {
+        "Date": {
+          "format": "date-time",
+          "title": "Date",
+          "type": "string"
+        },
+        "EntityType": {
+          "$ref": "#/$defs/BlockedUrlEntityType"
+        },
+        "RequestType": {
+          "$ref": "#/$defs/BlockedUrlRequestType"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "__type": {
+          "default": "BlockedUrl:#Microsoft.Bing.Webmaster.Api",
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "Date",
+        "EntityType",
+        "RequestType",
+        "Url"
+      ],
+      "title": "BlockedUrl",
+      "type": "object"
+    },
+    "BlockedUrlEntityType": {
+      "enum": [
+        0,
+        1
+      ],
+      "title": "BlockedUrlEntityType",
+      "type": "integer"
+    },
+    "BlockedUrlRequestType": {
+      "enum": [
+        0,
+        1
+      ],
+      "title": "BlockedUrlRequestType",
+      "type": "integer"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/BlockedUrl"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_blocked_urlsOutput",
+  "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 carries the full burden. It discloses pagination behavior ('Returns at most limit rows... call again with offset=next_offset') and the error type (BingWebmasterError), but does not mention permissions, rate limits, or side effects. As a read operation, this is adequate.

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 organized into Args, Returns, Raises, and a pagination note, with no redundant text. It is front-loaded with the primary purpose and uses clear formatting.

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 description covers purpose, parameters, return type, error, and pagination, which is sufficient for a read-only list tool with an output schema. It doesn't mention prerequisites like site ownership or verification, but these are likely common to all site tools and not critical for a basic call.

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 covers limit and offset with descriptions, but site_url lacks a schema description. The description's Args section defines site_url as 'The URL of the site', and the pagination note clarifies offset usage, adding 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 description states 'Get a list of blocked pages/directories for a site' with a specific verb and resource, clearly distinguishing it from sibling tools like add_blocked_url and remove_blocked_url. The return type is also specified.

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 its use for retrieving blocked URLs but does not explicitly contrast with add_blocked_url or remove_blocked_url. No when-to-use or when-not-to-use guidance is provided, leaving the agent to infer from the tool name.

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

Deploy Server