Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_query_parameters

Retrieve URL normalization parameters for a website to identify which query parameters should be considered for content consistency, such as sorting or filtering parameters that don't change page content.

Instructions

Get a list of URL normalization parameters for a site.

URL parameters are used to identify which URL parameters should be considered for URL normalization (e.g., sorting, filtering parameters that don't change the content).

Args: site_url: The URL of the site

Returns: List[QueryParameter]: List of query parameters configuration

Raises: BingWebmasterError: If parameters cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The decorated wrapper function that serves as the handler for the get_query_parameters tool. It executes the tool logic by calling the underlying url_management.UrlManagementService.get_query_parameters method on the service instance.
    @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_query_parameters' tool by creating and assigning the wrapped handler function, which is decorated with @mcp.tool().
    get_query_parameters = wrap_service_method(  # noqa: F841
        mcp, service, "urls", "get_query_parameters"
    )
  • Top-level invocation of tool registration function that includes the get_query_parameters tool among all Bing Webmaster tools.
    add_bing_webmaster_tools(mcp, bing_service)
  • Helper function that generates the MCP tool handler wrappers, preserving signatures and docstrings from the original service methods.
    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
  • Initializes the 'urls' service attribute on BingWebmasterService, which provides the underlying get_query_parameters method.
    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 the full burden of behavioral disclosure. It mentions that the tool returns a list and can raise an error, but lacks details on permissions required, rate limits, whether it's a read-only operation, or how it interacts with the site. For a tool that likely involves accessing webmaster data, this is insufficient.

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 with clear sections (description, Args, Returns, Raises) and uses bullet-like formatting. It's front-loaded with the core purpose. Some redundancy exists (e.g., repeating 'URL parameters' in the description), but overall it's efficient and easy to parse.

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 the complexity (webmaster tool with 2 parameters), no annotations, and an output schema (which handles return values), the description is moderately complete. It covers the purpose and one parameter well but misses behavioral context and the 'self' parameter. It's adequate as a baseline but has clear gaps for effective agent use.

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?

The description explicitly documents the 'site_url' parameter and its purpose ('The URL of the site'), adding meaningful context beyond the schema, which has 0% description coverage. However, it doesn't mention the 'self' parameter, leaving one of the two required parameters undocumented. Since schema coverage is 0%, the description compensates well but not fully.

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: 'Get a list of URL normalization parameters for a site.' It specifies the verb ('Get') and resource ('URL normalization parameters'), and explains what these parameters are used for. However, it doesn't explicitly differentiate from sibling tools like 'get_query_page_stats' or 'get_query_traffic_stats', which appear related but focus on statistics rather than configuration.

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 any prerequisites, context for usage, or exclusions. With many sibling tools related to queries and URLs (e.g., 'get_query_stats', 'get_query_page_stats'), the lack of differentiation leaves the agent without clear usage criteria.

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