mcp-server-bwt

by agalliani

Overview Schema Source Related Servers Discussions Admin

Python

Remote

add_page_preview_block

Block page previews for a URL in Bing Webmaster Tools by specifying the site and a blocking reason.

Instructions

Add a page preview block.

Args: site_url: The URL of the site url: The URL to block from page preview reason: The reason for blocking the page preview

Raises: BingWebmasterError: If preview block cannot be added

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>",
      "url": "<url>",
      "reason": "<reason>"
    },
    "name": "add_page_preview_block"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`reason`	Yes
`site_url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations are absent, so the description carries the full burden. It only mentions raising BingWebmasterError on failure, but doesn't disclose side effects, idempotency, reversibility, or what happens if the block already exists. For a mutation tool, this is insufficient behavioral disclosure.

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 concise and well-structured with an Args/Raises format. It is easy to parse and front-loads the action. However, the brevity contributes to missing details in other dimensions; conciseness itself is good.

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

Completeness2/5

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

The tool has 3 parameters with an enum, no annotations, and a minimal description. It lacks usage context, enum semantics, return value details, and any mention of prerequisites like site verification. Given the complexity of the Bing Webmaster domain, this description is incomplete.

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?

The description provides one-line meanings for each parameter: site_url, url, and reason. However, it doesn't explain the enum values for reason (1-4) as defined in the schema. Since schema description coverage is 0%, the description partially compensates but leaves the enum semantics ambiguous.

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 'Add a page preview block' with a clear verb and resource. It lists the three parameters with brief meanings, making the action specific. However, it doesn't explicitly differentiate from sibling tools like add_blocked_url or add_deep_link_block, and could clarify what a page preview block actually does in the Bing Webmaster context.

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?

No guidance is provided on when to use this tool versus alternatives such as add_blocked_url or add_deep_link_block. The description simply states the action without context, exclusions, or mention of scenarios where this tool is preferred. An agent would need to infer based on tool names alone.

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

Deploy Server