Skip to main content
Glama
Sign In
Bing Webmaster Tools MCP Server

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

add_blocked_url

Block a URL from Bing indexing by submitting it to your site's blocked list, choosing between page or directory and cache-only or full removal.

Instructions

Add a blocked URL to a site.

Args: site_url: The URL of the site blocked_url: The URL to be blocked entity_type: The type of entity to block (Page or Directory) request_type: The type of request (CacheOnly or FullRemoval) date: The date the URL was blocked (default: minimum datetime)

Raises: BingWebmasterError: If URL cannot be blocked

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_url": "<site_url>",
      "blocked_url": "<blocked_url>"
    },
    "name": "add_blocked_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
site_urlYes
blocked_urlYes
entity_typeNo
request_typeNo

Output 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",
-  "blocked_url"
-]New value: +[
+  "site_url",
+  "blocked_url"
+]
  2. Changed3 schema fields changedv1.0.0
    • addedInput schema / $defs / BlockedUrlRequestType
      Added value: +{
+  "enum": [
+    0,
+    1
+  ],
+  "title": "BlockedUrlRequestType",
+  "type": "integer"
+}
    • addedInput schema / properties / request_type
      Added value: +{
+  "$ref": "#/$defs/BlockedUrlRequestType",
+  "default": 0
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "null"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "add_blocked_urlOutput",
+  "type": "object"
+}
  3. First observed

TDQS

B3.1/5.0
Behavior2/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 of behavioral disclosure. For a mutation tool it only offers a minimal Raises clause (BingWebmasterError on failure) and omits what happens on success, reversibility, or permission requirements. 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.

Conciseness4/5

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

The docstring format front-loads a one-line purpose followed by an informative Args list and a compact Raises note. It is well-structured with no filler; the only low-value element is the minimal Raises clause, but it does not bloat the description.

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?

An output schema exists, so return-value explanation is not required. Parameters are thoroughly covered, but the description omits usage context and behavioral detail that a write operation with no annotations should supply, leaving the agent without guidance on when to call it.

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?

Schema description coverage is 0%, and the description fully compensates by documenting all 5 parameters, including the enum semantics (Page or Directory for entity_type, CacheOnly or FullRemoval for request_type) and the date default (minimum datetime). This adds meaning the schema itself does not provide.

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?

"Add a blocked URL to a site" states a specific verb and resource, and the parameter list clarifies the domain (Bing Webmaster URL blocking). It is distinguishable from sibling tools remove_blocked_url and get_blocked_urls by its operation, though it never names those siblings explicitly.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives. The description is purely declarative and leaves the agent to infer when blocking a URL is appropriate versus using remove_blocked_url.

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