Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_page_stats

Retrieve detailed traffic statistics for top-performing pages from Bing Webmaster Tools to analyze website performance and identify high-traffic content.

Instructions

Get detailed traffic statistics for top pages.

Args: site_url: The URL of the site

Returns: List[QueryStats]: List of query statistics for top pages

Raises: BingWebmasterError: If statistics cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The wrap_service_method function creates and decorates the actual handler for get_page_stats (and all tools), executing the external service method within the service context manager.
    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
  • Specific registration of the 'get_page_stats' tool by wrapping the traffic service's get_page_stats method.
    get_page_stats = wrap_service_method(mcp, service, "traffic", "get_page_stats")  # noqa: F841
  • Top-level call to register all Bing Webmaster tools, including get_page_stats.
    add_bing_webmaster_tools(mcp, bing_service)
  • Initializes the 'traffic' service attribute on BingWebmasterService, which provides the get_page_stats method.
    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. It mentions that it 'Raises: BingWebmasterError: If statistics cannot be retrieved,' which adds some error-handling context. However, it doesn't describe other important behaviors: whether this is a read-only operation, if it requires specific permissions, rate limits, pagination, or what 'top pages' means (e.g., by what metric or time frame). For a tool with no annotations, this leaves significant gaps.

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 and appropriately sized. It front-loads the purpose ('Get detailed traffic statistics for top pages.') and uses clear sections (Args, Returns, Raises) for additional details. Every sentence earns its place, with no redundant information. It could be slightly more concise by integrating the sections more fluidly, but overall it's efficient and easy to scan.

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 (a data retrieval tool with 2 parameters), the description is moderately complete. It benefits from having an output schema (implied by 'Returns: List[QueryStats]'), so it doesn't need to explain return values in detail. However, with no annotations and incomplete parameter semantics, it lacks context on permissions, rate limits, and sibling differentiation. It's adequate as a minimum viable description but has clear gaps that could hinder effective tool selection.

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 schema provides no parameter descriptions. The description lists 'site_url: The URL of the site' under 'Args,' which adds basic semantics for one parameter. However, it doesn't explain the 'self' parameter at all, leaving it undocumented. With 2 parameters and low coverage, the description partially compensates but fails to cover all parameters, resulting in incomplete 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: 'Get detailed traffic statistics for top pages.' It specifies the verb ('Get') and resource ('detailed traffic statistics for top pages'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_page_query_stats' or 'get_query_page_stats', which appear related but have slightly different names.

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 sibling tools like 'get_page_query_stats', 'get_query_page_stats', and 'get_query_traffic_stats' available, there's no indication of how this tool differs in scope or context. The description lacks any 'when-to-use' or 'when-not-to-use' information, leaving the agent to guess 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