Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

add_deep_link_block

Block unwanted deep links from Bing search results by adding a deep link block for a specific site, market, and search URL.

Instructions

Add a deep link block.

Args: site_url: The URL of the site market: The market code search_url: The search URL deep_link_url: The deep link URL to block

Raises: BingWebmasterError: If block cannot be added

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketYes
site_urlYes
search_urlYes
deep_link_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • removedInput schema / properties / self
      Removed value: -{
-  "title": "self",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "self",
-  "site_url",
-  "market",
-  "search_url",
-  "deep_link_url"
-]New value: +[
+  "site_url",
+  "market",
+  "search_url",
+  "deep_link_url"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "null"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "add_deep_link_blockOutput",
+  "type": "object"
+}
  3. First observed

TDQS

D1.3/5.0
Behavior1/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 only mentions that a BingWebmasterError may be raised, which is minor. It does not disclose side effects, idempotency, permissions, or what happens on success. For a mutation tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is short and avoids fluff, but it is under-specified. The docstring-style structure with Args and Raises is reasonable, but it lacks front-loaded context or any explanation of the tool's purpose beyond the first line. It is not conciseness that aids the agent; it is just too sparse.

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

Completeness1/5

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

Given the tool has four required parameters, no annotations, no parameter descriptions, and no explanation of the return value or behavior, the description is highly incomplete. An agent cannot correctly construct a call without guessing at the meaning of the parameters. The presence of an output schema is not mentioned, and no indication of what the response contains is given.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema lists four string parameters with no descriptions, and the description merely repeats their names without adding meaning. With schema description coverage at 0%, the description should compensate but does not explain the purpose, format, or constraints of site_url, market, search_url, or deep_link_url.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Add a deep link block,' which is a clear verb+resource, but it does not explain what a deep link block is or what the action entails. It does not differentiate from siblings like add_page_preview_block or remove_deep_link_block. It is not a tautology, but it is too vague to guide an agent that lacks domain-specific knowledge.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, scenarios, or exclusions. The agent is left to infer that this tool is for adding deep link blocks, but there is no comparison to remove_deep_link_block or other add tools.

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