Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_crawl_issues

Identify URLs with crawl issues on your site to help Bing's crawler access and process pages correctly. This tool retrieves a list of problematic URLs for analysis and resolution.

Instructions

Get a list of URLs with crawl issues for a specific site.

This helps identify pages that Bing's crawler had trouble accessing or processing.

Args: site_url: The URL of the site

Returns: List[UrlWithCrawlIssues]: List of URLs with their associated crawl issues

Raises: BingWebmasterError: If issues cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The async wrapper function generated by wrap_service_method that serves as the MCP tool handler for get_crawl_issues. It invokes the underlying crawling service's get_crawl_issues 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)
    
    # Copy signature and docstring
    wrapper.__signature__ = new_sig  # type: ignore
    wrapper.__doc__ = original_method.__doc__
  • Specific registration of the get_crawl_issues tool within the add_bing_webmaster_tools function.
    get_crawl_issues = wrap_service_method(mcp, service, "crawling", "get_crawl_issues")  # noqa: F841
  • Invokes the function that registers all Bing Webmaster tools, including get_crawl_issues, to the MCP server.
    # Add the tools to the MCP server
    add_bing_webmaster_tools(mcp, bing_service)
  • Mapping of service names to classes, used by wrap_service_method to retrieve the original method signature and docstring for get_crawl_issues.
    # Map service attribute names to their corresponding service classes
    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,
    }
  • Initialization of the crawling service instance within BingWebmasterService, which provides the get_crawl_issues method.
    self.traffic = traffic_analysis.TrafficAnalysisService(self.client)
    self.crawling = crawling.CrawlingService(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 but lacks behavioral details. It mentions the tool helps identify crawl issues but doesn't disclose rate limits, authentication requirements, pagination behavior, or what happens on errors beyond the generic BingWebmasterError. For a read operation with zero annotation coverage, this is insufficient.

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 purpose statement, explanation, and separate sections for Args, Returns, and Raises. It's appropriately sized with no redundant information, though the 'self' parameter documentation could be more explicit.

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

Completeness4/5

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

Given the tool's moderate complexity (2 parameters, read operation), the description provides good coverage: purpose, parameters, return type, and error handling. With an output schema present (List[UrlWithCrawlIssues]), it doesn't need to explain return values in detail. The main gap is behavioral context like rate limits or permissions.

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%, but the description explicitly documents both parameters in the Args section with clear meanings: 'site_url: The URL of the site' and implicitly 'self' (though less clear). It compensates well for the schema gap, though 'self' parameter semantics remain ambiguous.

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 verb ('Get') and resource ('list of URLs with crawl issues for a specific site'), specifying it's for Bing's crawler. It distinguishes from siblings like get_fetched_urls (which retrieves fetched URLs) or get_crawl_stats (which provides statistics rather than issues).

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

Usage Guidelines3/5

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

The description implies usage when needing to identify pages with crawl problems, but doesn't explicitly state when to use this versus alternatives like get_fetched_url_details (for specific URL issues) or get_crawl_settings (for configuration). No exclusions or prerequisites are mentioned.

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