Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_crawl_settings

Retrieve current crawl configuration for a website to monitor and adjust how Bing's search engine indexes your content.

Instructions

Retrieve crawl settings for a specific site.

Args: site_url: The URL of the site to get crawl settings for

Returns: CrawlSettings: The current crawl settings for the site

Raises: BingWebmasterError: If settings cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
__typeNoCrawlSettings:#Microsoft.Bing.Webmaster.Api
CrawlRateYes
CrawlBoostEnabledYes
CrawlBoostAvailableYes

Implementation Reference

  • Core execution logic of the get_crawl_settings tool: an async wrapper function decorated as @mcp.tool() that invokes the underlying CrawlingService.get_crawl_settings method via dynamic attribute access.
    @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_settings tool by invoking wrap_service_method with the crawling service and method name.
    get_crawl_settings = wrap_service_method(  # noqa: F841
        mcp, service, "crawling", "get_crawl_settings"
    )
  • Overall registration entry point: calls add_bing_webmaster_tools which includes the get_crawl_settings tool registration.
    add_bing_webmaster_tools(mcp, bing_service)
  • Helper function that generates the MCP tool handler for get_crawl_settings (and others) by inspecting the original service method signature and creating a decorated wrapper.
    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
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves settings and mentions a potential error ('BingWebmasterError'), but lacks critical details: whether it's read-only (implied but not explicit), authentication requirements, rate limits, or what happens if the site doesn't exist. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 and appropriately sized. It front-loads the purpose in the first sentence, followed by clear sections for Args, Returns, and Raises. There's minimal waste, though the 'self' parameter lacks explanation, slightly reducing efficiency. Overall, it's concise and organized.

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, retrieval operation), the description is reasonably complete. It explains the purpose, parameters, return value ('CrawlSettings'), and error handling. Since an output schema exists, it doesn't need to detail return values. However, it lacks usage guidelines and full behavioral context, preventing a perfect score.

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 schema provides no parameter documentation. The description adds value by explaining 'site_url' ('The URL of the site to get crawl settings for'), but it doesn't clarify 'self' (an undocumented parameter). With 2 parameters and partial coverage in the description, it meets the baseline for moderate compensation but doesn't fully address the schema gap.

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 tool's purpose: 'Retrieve crawl settings for a specific site.' It specifies the verb ('Retrieve'), resource ('crawl settings'), and scope ('for a specific site'), which distinguishes it from siblings like 'save_crawl_settings' (write operation) and 'get_crawl_stats' (different resource). However, it doesn't explicitly differentiate from all siblings (e.g., 'get_sites' is broader), so it's not a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., site must exist), exclusions, or comparisons to siblings like 'get_crawl_issues' or 'get_crawl_stats'. The agent must infer usage from the name and description alone, which is insufficient for clear decision-making.

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