Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix

get_rank_and_traffic_stats

Retrieve ranking positions and traffic data for a website from Bing Webmaster Tools to monitor search performance and analyze visitor trends.

Instructions

Get ranking and traffic statistics for a site.

Args: site_url: The URL of the site

Returns: List[RankAndTrafficStats]: List of ranking and traffic statistics

Raises: BingWebmasterError: If statistics cannot be retrieved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler logic for the tool (shared across all Bing Webmaster tools). It wraps the service method with @mcp.tool(), copies the signature and docstring, and executes the underlying traffic_analysis.TrafficAnalysisService.get_rank_and_traffic_stats method via the BingWebmasterService instance.
    # 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__
  • Specific registration of the 'get_rank_and_traffic_stats' tool by invoking the wrap_service_method helper with the appropriate service ('traffic') and method name.
    get_rank_and_traffic_stats = wrap_service_method(  # noqa: F841
        mcp, service, "traffic", "get_rank_and_traffic_stats"
    )
  • Overall registration entry point where all Bing Webmaster tools, including 'get_rank_and_traffic_stats', are added to the MCP server instance.
    add_bing_webmaster_tools(mcp, bing_service)
  • Initializes the 'traffic' service attribute on BingWebmasterService, which provides the underlying get_rank_and_traffic_stats method used by the tool.
    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 potential errors ('Raises: BingWebmasterError') and the return type, but lacks details on permissions, rate limits, data freshness, or whether this is a read-only operation. For a tool with no annotations, this is insufficient to inform safe and effective use.

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 sentences. It's front-loaded with the core purpose. However, the inclusion of 'Raises' adds necessary detail without being verbose, making it efficient but not perfectly concise due to the structured formatting.

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 (2 parameters, no annotations, but an output schema exists), the description is moderately complete. It explains the purpose and some parameters, and the output schema handles return values, but it misses behavioral context and full parameter documentation. This makes it adequate for basic use but lacking for robust agent operation.

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?

The description lists 'site_url' as an argument and notes it's 'The URL of the site,' but the input schema has two required parameters ('self' and 'site_url') with 0% schema description coverage. The description partially compensates by explaining 'site_url,' but ignores 'self' entirely, leaving a significant gap. Baseline 3 is appropriate as it adds some value but doesn't fully address the coverage deficit.

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 ranking and traffic statistics for a site.' It specifies the verb ('Get') and resource ('ranking and traffic statistics'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_query_traffic_stats' or 'get_url_traffic_info,' which prevents 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. With many sibling tools related to traffic and statistics (e.g., 'get_query_traffic_stats,' 'get_url_traffic_info'), there's no indication of context, prerequisites, or exclusions. This leaves the agent without clear usage 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