Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_query_stats

Retrieve detailed traffic statistics for top search queries from Bing Webmaster Tools to analyze site performance and identify high-performing keywords.

Instructions

Get detailed traffic statistics for top queries.

Args: site_url: The URL of the site

Returns: List[QueryStats]: List of statistics for top queries

Raises: BingWebmasterError: If statistics cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Generic handler creation and registration logic for the 'get_query_stats' MCP tool. Uses @mcp.tool() decorator on an async wrapper that delegates execution to the underlying traffic_analysis.TrafficAnalysisService.get_query_stats method, preserving original signature and documentation.
    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
  • Explicit registration of the 'get_query_stats' tool within the add_bing_webmaster_tools function by invoking the wrapper with the 'traffic' service attribute.
    get_query_stats = wrap_service_method(mcp, service, "traffic", "get_query_stats")  # noqa: F841
  • Attaches the TrafficAnalysisService instance (containing get_query_stats method) to the BingWebmasterService instance used by tool handlers.
    self.traffic = traffic_analysis.TrafficAnalysisService(self.client)
  • SERVICE_CLASSES dictionary maps 'traffic' to TrafficAnalysisService class, used by wrapper to retrieve method signature.
    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,
    }
  • Invokes add_bing_webmaster_tools to perform all tool registrations, including get_query_stats.
    add_bing_webmaster_tools(mcp, bing_service)
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 it 'Raises: BingWebmasterError: If statistics cannot be retrieved,' which adds some error-handling context. However, it lacks details on permissions, rate limits, data freshness, or what 'top queries' means (e.g., criteria, limit). For a read operation without annotations, 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 (Args, Returns, Raises) and front-loaded purpose. It's concise at 4 sentences, with no wasted words. However, the 'self' parameter is unexplained, and the purpose could be slightly more specific, but overall it's efficient.

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 tool's complexity (read operation with 2 parameters), no annotations, and an output schema (implied by 'Returns: List[QueryStats]'), the description is minimally adequate. It covers the basic purpose and one parameter but misses details on 'self', behavioral traits, and usage context. The output schema reduces the need to explain return values, but gaps remain.

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?

The schema description coverage is 0%, so the description must compensate. It lists 'site_url: The URL of the site' in the Args section, adding meaning for one parameter. However, it omits 'self', leaving it undocumented. With 2 parameters and only 50% covered in the description, it doesn't fully compensate for the schema gap.

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 detailed traffic statistics for top queries.' It specifies the verb ('Get') and resource ('traffic statistics for top queries'), making it understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_query_traffic_stats' or 'get_query_page_stats', which appear related, so it falls short of a perfect score.

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 mentions a 'site_url' parameter but doesn't explain prerequisites, context, or comparisons to sibling tools such as 'get_query_traffic_stats' or 'get_page_query_stats'. This lack of usage context leaves the agent with minimal 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