Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

remove_query_parameter

Remove URL normalization parameters from your website to improve search engine indexing and prevent duplicate content issues in Bing Webmaster Tools.

Instructions

Remove a URL normalization parameter from a site.

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

Raises: BingWebmasterError: If parameter cannot be removed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
query_parameterYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Registers the 'remove_query_parameter' tool as an MCP tool by wrapping the 'remove_query_parameter' method from the 'urls' (UrlManagementService) using the generic wrapper. The wrapper is decorated with @mcp.tool() and preserves the original method's signature and docstring.
    remove_query_parameter = wrap_service_method(  # noqa: F841
        mcp, service, "urls", "remove_query_parameter"
  • Generic helper function that creates the MCP tool handler for 'remove_query_parameter' (and all other tools). It inspects the original service method signature, creates a wrapper decorated with @mcp.tool(), and delegates execution to the underlying service instance method.
    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 service attribute names like 'urls' to their corresponding service classes (UrlManagementService), used by wrap_service_method to locate the original method for wrapping.
    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,
    }
  • Calls the function that performs all tool registrations, including 'remove_query_parameter', initializing the MCP server with Bing Webmaster Tools.
    add_bing_webmaster_tools(mcp, bing_service)
  • Initializes the 'urls' service instance on BingWebmasterService, which provides the 'remove_query_parameter' method that gets wrapped into the MCP tool.
    self.urls = url_management.UrlManagementService(self.client)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions that removal might fail with a 'BingWebmasterError', which adds some behavioral context, but doesn't cover critical aspects like required permissions, whether the change is reversible, or rate limits. This leaves significant gaps for a mutation tool.

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 structured with a purpose statement followed by Args and Raises sections, which is clear. However, the 'self' parameter is unexplained, and the text could be more front-loaded with critical usage information, making it somewhat inefficient.

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 that there's an output schema (which handles return values) but no annotations and low schema coverage, the description is moderately complete. It covers basic purpose and error handling but lacks details on parameters, permissions, and behavioral traits, which are important for a mutation tool in this context.

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 the parameters ('site_url', 'query_parameter') and provides a brief explanation in the Args section, but doesn't clarify the purpose of the 'self' parameter or provide examples or formatting details. This is insufficient for a tool with 3 undocumented parameters.

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 ('Remove') and resource ('URL normalization parameter from a site'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'remove_blocked_url' or 'enable_disable_query_parameter', which handle related but different operations.

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. With siblings like 'add_query_parameter' and 'enable_disable_query_parameter', the description doesn't explain the specific context for removal versus other parameter management operations.

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