Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_blocked_urls

Retrieve blocked pages and directories for a site. Get a list of URLs blocked by Bing Webmaster Tools with their settings to identify and manage blocked content.

Instructions

Get a list of blocked pages/directories for a site.

Args: site_url: The URL of the site

Returns: List[BlockedUrl]: List of blocked URLs and their settings

Raises: BingWebmasterError: If blocked URLs cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `wrap_service_method` function is the generic handler wrapper that dynamically wraps any service method as an MCP tool. For 'get_blocked_urls', it wraps `content_blocking.ContentBlockingService.get_blocked_urls` by calling `wrap_service_method(mcp, service, 'blocking', 'get_blocked_urls')`.
    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
  • The registration line that creates the 'get_blocked_urls' MCP tool by wrapping the 'get_blocked_urls' method from the 'blocking' (ContentBlockingService) service.
    get_blocked_urls = wrap_service_method(mcp, service, "blocking", "get_blocked_urls")  # noqa: F841
  • The service initialization in `__aenter__` where `self.blocking` is instantiated as `content_blocking.ContentBlockingService(self.client)`, which is the service object whose `get_blocked_urls` method will be called.
    async def __aenter__(self) -> "BingWebmasterService":
        self.client = BingWebmasterClient(self.settings)
        await self.client.__aenter__()
    
        # Expose all services directly
        self.sites = site_management.SiteManagementService(self.client)
        self.submission = submission.SubmissionService(self.client)
        self.traffic = traffic_analysis.TrafficAnalysisService(self.client)
        self.crawling = crawling.CrawlingService(self.client)
        self.keywords = keyword_analysis.KeywordAnalysisService(self.client)
        self.links = link_analysis.LinkAnalysisService(self.client)
        self.content = content_management.ContentManagementService(self.client)
        self.blocking = content_blocking.ContentBlockingService(self.client)
        self.regional = regional_settings.RegionalSettingsService(self.client)
        self.urls = url_management.UrlManagementService(self.client)
  • The SERVICE_CLASSES mapping that maps 'blocking' to `content_blocking.ContentBlockingService`, used by `wrap_service_method` to resolve the service class and its methods.
    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,
    }
  • The main entry point that creates the MCP server and calls `add_bing_webmaster_tools(mcp, bing_service)` which registers all tools including 'get_blocked_urls'.
    import os
    from mcp.server.fastmcp import FastMCP
    from mcp_server_bwt.services.bing_webmaster import BingWebmasterService
    from mcp_server_bwt.tools.bing_webmaster import add_bing_webmaster_tools
    
    mcp = FastMCP("mcp-server-bwt")
    
    # Initialize Bing Webmaster Tools service
    api_key = os.getenv("BING_WEBMASTER_API_KEY")
    if not api_key:
        raise ValueError("BING_WEBMASTER_API_KEY environment variable is required")
    
    # Create the service with the API key
    bing_service = BingWebmasterService(api_key=api_key)
    
    # Add the tools to the MCP server
    add_bing_webmaster_tools(mcp, bing_service)
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states it returns a list and can raise an error. It does not mention if it's read-only, requires authentication, or any side effects, leaving the behavior under-specified.

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

Conciseness3/5

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

The description is concise but incomplete: it documents only one of two parameters. The structure with Args, Returns, Raises is good but the missing 'self' parameter is a notable gap.

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 two required parameters and an output schema, but the description adds little beyond the schema. It does not explain what blocked URLs are, the format of settings, or how pagination works (if any). For a retrieval tool, more context is needed.

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 input schema has two parameters (self, site_url), but the description only documents site_url. With 0% schema description coverage, the description should add meaning to the undocumented 'self' parameter, but it does not. This fails to help the agent understand parameter semantics.

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

Purpose5/5

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

The description clearly states the tool retrieves a list of blocked pages/directories for a site, using a specific verb+resource pattern. This distinguishes it from siblings like add_blocked_url, remove_blocked_url, and get_connected_pages.

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

Usage Guidelines4/5

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

The description provides the required argument 'site_url' and indicates it returns a list of BlockedUrl objects. While it doesn't explicitly state when to use this tool versus alternatives, the context of retrieving blocked URLs is clear.

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