Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

add_query_parameter

Add a URL normalization parameter to a website in Bing Webmaster Tools to manage how search engines handle query strings and improve indexing accuracy.

Instructions

Add a URL normalization parameter for a site.

Args: site_url: The URL of the site query_parameter: The query parameter to add

Raises: BingWebmasterError: If parameter cannot be added

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
query_parameterYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registers the MCP tool 'add_query_parameter' by wrapping the 'add_query_parameter' method from the 'urls' (UrlManagementService) using the generic wrap_service_method helper.
    add_query_parameter = wrap_service_method(  # noqa: F841
        mcp, service, "urls", "add_query_parameter"
    )
  • The dynamically defined handler function that executes the tool logic: enters the service context, retrieves the sub-service and method, and invokes it with the provided arguments.
    # 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__
  • Helper function that generates the MCP tool handler for any service method, including signature inspection and preservation for input validation (schema).
    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?

With no annotations provided, the description carries full burden but lacks behavioral details. It mentions raising 'BingWebmasterError' on failure, hinting at external API interaction, but doesn't disclose permissions needed, rate limits, side effects (e.g., if this affects site indexing), or response format. For a mutation tool, this is insufficient 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 front-loaded with the main purpose, followed by structured 'Args' and 'Raises' sections, making it efficient. However, the 'Args' section could be integrated more seamlessly, and some redundancy exists (e.g., repeating parameter names without extra context), but overall it's well-organized with minimal waste.

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 3 parameters with 0% schema coverage, no annotations, but an output schema exists, the description is partially complete. It covers the basic purpose and error handling but lacks details on parameters, behavioral traits, and usage context. The output schema may handle return values, but for a mutation tool, more guidance is needed to be fully adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 lists 'site_url' and 'query_parameter' with brief notes, but omits 'self' entirely, leaving one parameter undocumented. The notes are minimal (e.g., 'The URL of the site'), adding little meaning beyond what the schema titles imply, failing to address the coverage gap.

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

Purpose3/5

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

The description states the tool 'Add a URL normalization parameter for a site,' which clarifies the action (add) and resource (URL normalization parameter). However, it's vague about what 'URL normalization parameter' means—it could be a query parameter for URL canonicalization or SEO purposes. It doesn't distinguish from siblings like 'enable_disable_query_parameter' or 'remove_query_parameter,' leaving ambiguity in scope.

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. Sibling tools like 'enable_disable_query_parameter' or 'remove_query_parameter' suggest related functionality, but the description offers no context, prerequisites, or exclusions for usage, leaving the agent to infer based on tool names alone.

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