Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_deep_link_algo_urls

Retrieve algorithmically generated URLs with deep links from Bing Webmaster Tools for a given site. Use offset and limit to paginate through results.

Instructions

Get algo URLs with deep links. (Deprecated)

Args: site_url: The URL of the site

Returns: List[DeepLinkAlgoUrl]: List of algo URLs with deep links

Raises: BingWebmasterError: If algo 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
NameRequiredDescriptionDefault
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"
-]New value: +[
+  "site_url"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "DeepLinkAlgoUrl": {
+      "properties": {
+        "DeepLinkCount": {
+          "title": "Deeplinkcount",
+          "type": "integer"
+        },
+        "Impressions": {
+          "title": "Impressions",
+          "type": "integer"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "DeepLinkCount",
+        "Impressions",
+        "Url"
+      ],
+      "title": "DeepLinkAlgoUrl",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/DeepLinkAlgoUrl"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_deep_link_algo_urlsOutput",
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses the error type (BingWebmasterError), mentions the deprecation, and documents pagination behavior. It does not specify auth requirements, whether it is read-only, or any side effects. It offers moderate transparency but lacks depth.

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?

Well-structured with a clear one-line summary followed by Args/Returns/Raises and pagination notes. Information is front-loaded and each line serves a purpose. Slightly verbose with the docstring format, but appropriate for a deprecated tool.

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?

Output schema exists, so return format is covered elsewhere. The description includes error handling and pagination. The main gap is the lack of a replacement reference given the deprecation, and no mention of typical use cases or constraints beyond pagination. Adequate but not comprehensive.

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 description coverage is 67%, so the schema already documents 'limit' and 'offset' clearly. The description only restates site_url as 'The URL of the site' which adds little. It does reference offset in the pagination context, which adds practical meaning. Overall it neither fully compensates for the uncovered site_url nor adds substantial new meaning.

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 one-liner 'Get algo URLs with deep links.' states a specific verb and resource. The deprecation marker adds clarity about its current status. It does not explicitly distinguish from sibling deep-link tools like get_deep_link or get_deep_link_blocks, but the 'algo URLs' qualifier is reasonably specific.

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?

Provides concrete pagination instructions ('call again with offset=next_offset'), which is practical usage guidance. However, it does not explain when to prefer this tool over alternatives, nor does it mention a replacement given the deprecation. No when-not guidance is present.

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