Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_deep_link

Retrieve deep links for a specific URL on your site to analyze link structure and improve search visibility.

Instructions

Get deep links for a specific algo URL. (Deprecated)

Args: site_url: The URL of the site url: The specific URL to get deep links for

Returns: List[DeepLink]: List of deep links

Raises: BingWebmasterError: If deep links 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
NameRequiredDescriptionDefault
urlYes
limitNoMaximum number of rows to return.
offsetNoIndex of the first row.
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • 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"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "DeepLink": {
+      "properties": {
+        "Position": {
+          "title": "Position",
+          "type": "integer"
+        },
+        "Title": {
+          "title": "Title",
+          "type": "string"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "Weight": {
+          "title": "Weight",
+          "type": "integer"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Position",
+        "Title",
+        "Url",
+        "Weight"
+      ],
+      "title": "DeepLink",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/DeepLink"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_deep_linkOutput",
+  "type": "object"
+}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It does mention deprecation, pagination (limit/offset/next_offset), and a specific exception (BingWebmasterError). However, it omits other behavioral traits like whether it's read-only, authentication requirements, or rate limits. The pagination and deprecation are valuable, but the picture is incomplete.

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 compact and logically ordered: purpose, deprecation, args, returns, raises, and pagination note. It front-loads the key action and deprecation. No wasted words, though the Args section could be considered redundant with the schema, but it's acceptable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple getter with pagination, the description covers the mechanics well, but it fails to guide the agent on the deprecation—no alternative tool is suggested, and 'algo URL' remains undefined. The output schema exists, so return details aren't required, but the missing deprecation guidance and unclear terminology leave the agent without full context for correct use.

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 50% (only limit and offset have descriptions). The description adds brief meanings for site_url and url, which the schema lacks, and explains the pagination interaction. However, it doesn't clarify what 'algo URL' means or expand on the parameters beyond what schema states, so it partially compensates for the gap but not fully.

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 the action ('Get deep links') and the resource ('a specific algo URL'), which is clear enough to identify the core function. However, the term 'algo URL' is jargon and not defined, and it doesn't differentiate from sibling tools like get_deep_link_algo_urls or get_deep_link_blocks. It is more specific than a tautology, so a 4 is appropriate.

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, despite being marked 'Deprecated'. It doesn't name a replacement or suggest conditions for use, leaving the agent to guess whether this should be preferred or avoided. The pagination note is about how to use, not when to use.

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

Deploy Server

Other Tools