Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

remove_blocked_url

Unblock URLs from Bing Webmaster Tools to restore indexing and crawling access for specific pages or directories on your website.

Instructions

Remove a blocked URL from a site.

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

Raises: BingWebmasterError: If URL cannot be unblocked

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
blocked_urlYes
entity_typeNo
request_typeNo
dateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core handler logic for executing the remove_blocked_url tool. This wrapper function is dynamically created for each tool and delegates to the underlying ContentBlockingService.remove_blocked_url method.
    @mcp.tool()
    @wraps(original_method)
    async def wrapper(*args: Any, **kwargs: Any) -> Any:
        # Filter out any 'self' arguments that might be passed by the MCP client
        kwargs = {k: v for k, v in kwargs.items() if k != "self"}
    
        async with service as s:
            service_obj = getattr(s, service_attr)
            # Get the method from the instance
            method = getattr(service_obj, method_name)
            # Call the method directly - it's already bound to the instance
            return await method(*args, **kwargs)
  • Registers the 'remove_blocked_url' tool by wrapping the service method with MCP tool decorator.
    remove_blocked_url = wrap_service_method(  # noqa: F841
        mcp, service, "blocking", "remove_blocked_url"
    )
  • Invokes the tool registration function which includes the remove_blocked_url tool.
    add_bing_webmaster_tools(mcp, bing_service)
  • Initializes the ContentBlockingService instance (self.blocking) which provides the remove_blocked_url method used by the tool.
    self.blocking = content_blocking.ContentBlockingService(self.client)
  • Maps the 'blocking' service attribute to ContentBlockingService class for use in tool wrappers.
    "blocking": content_blocking.ContentBlockingService,
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the mutation nature ('Remove'), potential errors ('Raises: BingWebmasterError'), and hints at behavioral complexity through the 'request_type' parameter (CacheOnly/FullRemoval). However, it lacks details on permissions needed, rate limits, whether the operation is reversible, or what the output contains despite having an output schema.

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 well-structured with a clear purpose statement followed by Args and Raises sections. Every sentence earns its place by defining parameters and error conditions. It could be slightly more front-loaded with a brief usage hint, but overall it's efficient without wasted words.

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 mutation tool with 6 parameters, 0% schema coverage, no annotations, but an output schema, the description does an adequate job. It covers parameter semantics and error handling, but lacks behavioral context like permissions, side effects, or output expectations. The existence of an output schema reduces the need to describe return values, but more operational guidance would help.

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%, so the description must compensate. It provides semantic meaning for all 6 parameters beyond their names, explaining what each represents (e.g., 'entity_type: The type of entity to unblock (Page or Directory)'). This adds significant value, though it doesn't explain the enum values (0/1 for entity_type and request_type) or format details for 'date'.

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 clearly states the action ('Remove a blocked URL') and resource ('from a site'), making the purpose immediately understandable. It distinguishes from sibling 'add_blocked_url' by specifying removal rather than addition, though it doesn't explicitly contrast with other URL management tools like 'remove_deep_link_block' or 'remove_page_preview_block'.

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. While it's clear this removes blocked URLs, there's no mention of prerequisites (e.g., needing blocked URLs to exist), related tools like 'get_blocked_urls' for discovery, or when to choose 'CacheOnly' vs 'FullRemoval' request types. The description assumes the user already knows the context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zizzfizzix/mcp-server-bwt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server