Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_query_page_stats

Retrieve detailed traffic statistics for web pages that match a specific search query from Bing Webmaster Tools.

Instructions

Get detailed traffic statistics for pages matching a specific query.

Args: site_url: The URL of the site query: The search query to get statistics for

Returns: List[QueryStats]: List of page statistics for the query

Raises: BingWebmasterError: If statistics cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core handler logic for the tool execution. Decorates the wrapper function as an MCP tool, processes arguments, instantiates the service, and delegates the call to traffic_analysis_service.get_query_page_stats.
    @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__
  • Registers the "get_query_page_stats" tool by invoking wrap_service_method with the appropriate service attribute ("traffic") and method name.
    get_query_page_stats = wrap_service_method(  # noqa: F841
        mcp, service, "traffic", "get_query_page_stats"
    )
  • Helper function that generates the tool handler for service methods, preserving signature and documentation, used for get_query_page_stats among others.
    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
  • Top-level call to register all Bing Webmaster tools, including get_query_page_stats.
    add_bing_webmaster_tools(mcp, bing_service)
  • Initializes the TrafficAnalysisService instance (self.traffic) which provides the get_query_page_stats method delegated by the tool handler.
    self.traffic = traffic_analysis.TrafficAnalysisService(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. While it mentions that it returns 'List[QueryStats]' and can raise 'BingWebmasterError', it doesn't describe important behavioral aspects like whether this is a read-only operation, what permissions are required, rate limits, or what specific data the QueryStats contains. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 (Args, Returns, Raises) and uses minimal, purposeful sentences. The opening statement efficiently conveys the core purpose. While the structure is good, the content within each section could be more detailed given the lack of annotations and schema documentation.

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 (though not shown here), the description doesn't need to fully explain return values. However, with no annotations, 3 parameters (one undocumented), and a mutation-heavy sibling set, the description should provide more context about permissions, side effects, and error conditions. It mentions an error type but doesn't explain when it occurs or what permissions are needed.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter documentation. The description adds basic semantics for 'site_url' and 'query' parameters, explaining they identify the site and search query respectively. However, it doesn't explain the 'self' parameter at all, leaving one of three parameters completely undocumented. The description provides some value but doesn't fully compensate for the schema's lack of documentation.

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 with a specific verb ('Get') and resource ('detailed traffic statistics for pages matching a specific query'). It distinguishes itself from siblings like 'get_page_stats' or 'get_query_stats' by focusing on page-level statistics for a query. However, it doesn't explicitly contrast with 'get_query_page_detail_stats' which appears to be a very similar sibling.

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. With siblings like 'get_page_stats', 'get_query_stats', and 'get_query_page_detail_stats' available, there's no indication of when this specific query-page-stats tool is appropriate versus those other options. The description only states what it does, not when to choose it.

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