Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

remove_deep_link_block

Unblocks a specific deep link URL in Bing Webmaster Tools to restore its visibility in search results for a given site and market.

Instructions

Remove 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 unblock

Raises: BingWebmasterError: If block cannot be removed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
marketYes
search_urlYes
deep_link_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registers the 'remove_deep_link_block' MCP tool by wrapping the corresponding method from the LinkAnalysisService (accessed via BingWebmasterService.links). The wrapper preserves the original method's signature and docstring, and delegates execution to the service instance.
    remove_deep_link_block = wrap_service_method(  # noqa: F841
        mcp, service, "links", "remove_deep_link_block"
  • Defines the generic handler logic for all service-based tools, including remove_deep_link_block. Creates an async wrapper decorated as @mcp.tool(), extracts signature from original service method (skipping 'self'), calls the bound instance method within the service context manager.
    def wrap_service_method(
        mcp: FastMCP, service: BingWebmasterService, service_attr: str, method_name: str
    ) -> Callable[..., Any]:
        """Helper function to wrap a service method with mcp.tool() while preserving its signature and docstring.
    
        Args:
            mcp: The MCP server instance
            service: The BingWebmasterService instance
            service_attr: The service attribute name (e.g., 'sites', 'submission')
            method_name: The method name to wrap
    
        Returns:
            The wrapped method as an MCP tool
        """
        # Get the service class from our mapping
        service_class = SERVICE_CLASSES[service_attr]
        # Get the original method
        original_method = getattr(service_class, method_name)
        # Get the signature
        sig = inspect.signature(original_method)
        # Remove 'self' parameter from signature
        parameters = list(sig.parameters.values())[1:]  # Skip 'self'
    
        # Create new signature without 'self'
        new_sig = sig.replace(parameters=parameters)
    
        # Create wrapper function with same signature
        @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)
    
        # Copy signature and docstring
        wrapper.__signature__ = new_sig  # type: ignore
        wrapper.__doc__ = original_method.__doc__
    
        return wrapper
  • Maps service attribute names (e.g., 'links') to their class types, used in wrap_service_method to inspect the original method signature.
    SERVICE_CLASSES = {
        "sites": site_management.SiteManagementService,
        "submission": submission.SubmissionService,
        "traffic": traffic_analysis.TrafficAnalysisService,
        "crawling": crawling.CrawlingService,
        "keywords": keyword_analysis.KeywordAnalysisService,
        "links": link_analysis.LinkAnalysisService,
        "content": content_management.ContentManagementService,
        "blocking": content_blocking.ContentBlockingService,
        "regional": regional_settings.RegionalSettingsService,
        "urls": url_management.UrlManagementService,
    }
  • Invokes the function that registers all Bing Webmaster tools, including remove_deep_link_block, on the MCP server instance.
    add_bing_webmaster_tools(mcp, bing_service)
  • Initializes the 'links' service attribute on BingWebmasterService instance, which provides the remove_deep_link_block method.
    self.links = link_analysis.LinkAnalysisService(self.client)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action is 'Remove' (implying a destructive mutation) and mentions an error case ('BingWebmasterError: If block cannot be removed'), which adds some context about potential failures. However, it lacks critical details like required permissions, side effects, confirmation prompts, or what 'removing' entails operationally (e.g., permanent vs. reversible).

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 appropriately sized and front-loaded with the core purpose in the first sentence. The Args and Raises sections are structured for clarity. However, the 'self' parameter is listed without explanation, and the tool name repetition in the schema title is redundant, slightly reducing efficiency.

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?

Given 5 parameters with 0% schema coverage and no annotations, the description provides basic parameter semantics and an error case, but lacks details on behavioral traits, usage context, and output (though an output schema exists, mitigating the need to explain return values). For a destructive operation with multiple inputs, this is minimally adequate but has clear gaps in guidance and transparency.

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 0%, so the description must compensate. It lists all 5 parameters with brief explanations, adding meaning beyond the schema's bare titles. However, the explanations are minimal (e.g., 'The URL of the site' for site_url) and don't clarify format expectations, dependencies between parameters, or what 'self' refers to. This provides basic semantics but leaves significant gaps.

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') and target resource ('a deep link block'), which is specific and unambiguous. It distinguishes from sibling tools like 'add_deep_link_block' by indicating the opposite operation. However, it doesn't fully explain what a 'deep link block' is in this context, leaving some domain knowledge assumed.

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 explicit guidance on when to use this tool versus alternatives is provided. While the sibling list includes related tools like 'remove_blocked_url' and 'get_deep_link_blocks', the description doesn't clarify the relationship or differentiation between them. The only contextual hint is the error case mentioned, but no proactive usage advice.

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