Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

save_crawl_settings

Update crawl settings for a site to control crawl rate and boost availability in Bing Webmaster Tools.

Instructions

Save new crawl settings for a specific site.

Args: site_url: The URL of the site crawl_settings: The new crawl settings to apply

Raises: BingWebmasterError: If settings cannot be saved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
crawl_settingsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registration of 'save_crawl_settings' as an MCP tool via wrap_service_method, binding to the 'crawling' service's save_crawl_settings method.
    save_crawl_settings = wrap_service_method(  # noqa: F841
        mcp, service, "crawling", "save_crawl_settings"
    )
  • The generic wrap_service_method helper that dynamically creates an MCP tool handler for any service method. For save_crawl_settings, it resolves to CrawlingService.save_crawl_settings from the bing_webmaster_tools library.
    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 'crawling' to CrawlingService class, used by wrap_service_method to find the correct service class for save_crawl_settings.
    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,
    }
  • Instantiation of CrawlingService on the service object so that wrap_service_method can call the save_crawl_settings method on it at runtime.
    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)
  • Top-level invocation that registers all tools (including save_crawl_settings) onto 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 present, so the description must compensate. It mentions saving settings but lacks details on overwriting behavior, required permissions, or error conditions beyond a generic exception.

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 very short but includes an Args list that is not structured as clear schema documentation. It is concise but sacrifices completeness.

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

Completeness1/5

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

With 3 parameters, no descriptions, no behavioral details, and annotations missing, the description fails to provide sufficient context for an AI agent to use the tool correctly, especially for a write operation.

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?

Schema coverage is 0%, and the description only lists site_url and crawl_settings without explaining their meaning or format. The 'self' parameter is omitted entirely, and the CrawlSettings type fields are not described.

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 'save' and resource 'crawl settings' for a specific site, distinguishing it from sibling tools like get_crawl_settings.

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, alternatives, or prerequisites (e.g., verifying the site first). Only a brief description of the action.

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