Bing Webmaster Tools MCP Server

get_deep_link_blocks

Retrieve deep link blocks for a site to identify URLs that Bing excludes from deep link display. Use offset and limit to paginate through results.

Instructions

Get deep link blocks for a site.

Args: site_url: The URL of the site

Returns: List[DeepLinkBlock]: List of deep link blocks

Raises: BingWebmasterError: If blocks 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": {
+    "DeepLinkBlock": {
+      "properties": {
+        "BlockDate": {
+          "format": "date-time",
+          "title": "Blockdate",
+          "type": "string"
+        },
+        "DeepLinkUrl": {
+          "title": "Deeplinkurl",
+          "type": "string"
+        },
+        "Market": {
+          "title": "Market",
+          "type": "string"
+        },
+        "SearchUrl": {
+          "title": "Searchurl",
+          "type": "string"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Market",
+        "SearchUrl",
+        "DeepLinkUrl",
+        "BlockDate"
+      ],
+      "title": "DeepLinkBlock",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/DeepLinkBlock"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_deep_link_blocksOutput",
+  "type": "object"
+}

First observedApr 11, 2025

TDQS

A3.9/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 burden of disclosing behavior. It states the return type (List[DeepLinkBlock]), potential error (BingWebmasterError), and explains pagination via limit, offset, and next_offset. It does not explicitly state that the operation is read-only, but the 'get' verb implies this, and the pagination detail is 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with Args/Returns/Raises sections and includes a brief pagination note. It is not overly long, but the formatting adds some verbosity. The core purpose is front-loaded, and each sentence contributes useful information.

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 output schema (List[DeepLinkBlock]) and the description covering error handling and pagination, the tool is adequately documented for an agent to call it correctly. It lacks explicit mention of authentication prerequisites or whether the operation is read-only, but these are common and implied by the 'get' prefix.

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 has no description; the description fills that gap with 'The URL of the site.' Additionally, the description explains how limit and offset relate to pagination (next_offset), adding semantic value beyond the schema's simple type constraints.

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 opens with a specific verb and resource: 'Get deep link blocks for a site.' It clearly distinguishes from sibling tools like get_deep_link (singular) and add_deep_link_block by focusing on retrieval of blocks for a site, and the mention of returning a list reinforces the scope.

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 does not mention when to use this tool versus alternatives such as get_deep_link, add_deep_link_block, or remove_deep_link_block. It provides no conditions for selection, exclusions, or comparisons to sibling tools, leaving the agent to infer usage from the name alone.

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

Deploy Server