Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

enable_disable_query_parameter

Control URL normalization for Bing Webmaster Tools by enabling or disabling specific query parameters on your site to manage how search engines process URLs.

Instructions

Enable or disable a URL normalization parameter for a site.

Args: site_url: The URL of the site query_parameter: The query parameter to enable/disable is_enabled: True to enable, False to disable

Raises: BingWebmasterError: If parameter state cannot be updated

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
query_parameterYes
is_enabledYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registers the 'enable_disable_query_parameter' tool using wrap_service_method, which decorates a wrapper function with @mcp.tool() to expose the underlying url_management.UrlManagementService.enable_disable_query_parameter as an MCP tool.
    enable_disable_query_parameter = wrap_service_method(  # noqa: F841
        mcp, service, "urls", "enable_disable_query_parameter"
    )
  • The wrap_service_method function creates and returns the actual handler for the tool (an async wrapper decorated with @mcp.tool()), which calls the underlying service method on the 'urls' service instance.
    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
  • In BingWebmasterService.__aenter__, initializes the 'urls' attribute with UrlManagementService(client), providing the underlying service instance used by the tool handler.
    self.urls = url_management.UrlManagementService(self.client)
  • Calls add_bing_webmaster_tools to register all Bing Webmaster tools, including 'enable_disable_query_parameter', on the MCP server instance.
    add_bing_webmaster_tools(mcp, bing_service)
  • SERVICE_CLASSES maps 'urls' to url_management.UrlManagementService class, used in wrap_service_method to get the original method signature.
    "urls": url_management.UrlManagementService,
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 offers minimal behavioral insight. It mentions that an error ('BingWebmasterError') may be raised if the update fails, which is useful, but lacks details on permissions, side effects, rate limits, or what 'URL normalization parameter' entails operationally.

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 front-loaded with the core purpose, followed by parameter explanations and error handling. It's efficient with no wasted sentences, though the 'self' parameter remains unexplained, slightly reducing completeness.

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 4 parameters with 0% schema coverage and no annotations, the description does a decent job explaining most parameters and noting potential errors. However, it lacks details on the 'self' parameter, behavioral traits like side effects, and the presence of an output schema means return values aren't addressed, which is acceptable but leaves some gaps.

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%, so the description must compensate. It clearly explains all four parameters: 'site_url' as the site URL, 'query_parameter' as the parameter to modify, and 'is_enabled' with its boolean meaning. This adds significant value beyond the bare schema, though it doesn't clarify the 'self' parameter's purpose.

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 ('enable or disable'), the resource ('URL normalization parameter'), and the target ('for a site'). It uses specific verbs and identifies the resource type, though it doesn't explicitly differentiate from sibling tools like 'add_query_parameter' or 'remove_query_parameter'.

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 versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or contrast with sibling tools like 'add_query_parameter' or 'remove_query_parameter', leaving the agent without usage direction.

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