Skip to main content
Glama
isiahw1

mcp-server-bing-webmaster

get_page_stats

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

Instructions

Get traffic statistics for top pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_page_stats' tool, decorated with @mcp.tool for registration. It fetches traffic statistics for top pages of a site by calling the Bing Webmaster API's GetPageStats endpoint and processes the response.
    @mcp.tool(name="get_page_stats", description="Get traffic statistics for top pages.")
    async def get_page_stats(
        site_url: Annotated[str, "The URL of the site"]
    ) -> List[Dict[str, Any]]:
        """
        Get traffic statistics for top pages.
    
        Args:
            site_url: The URL of the site
    
        Returns:
            List of page statistics
        """
        async with api:
            stats = await api._make_request(f"GetPageStats?siteUrl={site_url}")
            return api._ensure_type_field(stats, "PageStats")
  • Helper method in BingWebmasterAPI class used by get_page_stats to ensure the response data has the required __type field for MCP compatibility.
    def _ensure_type_field(self, data: Any, type_name: str) -> Any:
        """Ensure __type field is present for MCP compatibility."""
        if isinstance(data, list):
            for item in data:
                if isinstance(item, dict) and "__type" not in item:
                    item["__type"] = f"{type_name}:#Microsoft.Bing.Webmaster.Api"
        elif isinstance(data, dict) and "__type" not in data:
            data["__type"] = f"{type_name}:#Microsoft.Bing.Webmaster.Api"
        return data
  • Core helper method in BingWebmasterAPI used by get_page_stats to make HTTP requests to the Bing Webmaster API, handle responses, and OData formatting.
    async def _make_request(
        self,
        endpoint: str,
        method: str = "GET",
        json_data: Optional[Dict[str, Any]] = None,
        params: Optional[Dict[str, Any]] = None,
    ) -> Any:
        """Make a request to the Bing API and handle OData responses."""
        if not self.client:
            raise RuntimeError(
                "API client not initialized. Use 'async with api:' context manager."
            )
    
        headers = {"Content-Type": "application/json; charset=utf-8"}
    
        # Build URL with API key
        if "?" in endpoint:
            url = f"{self.base_url}/{endpoint}&apikey={self.api_key}"
        else:
            url = f"{self.base_url}/{endpoint}?apikey={self.api_key}"
    
        # Add additional parameters if provided
        if params:
            for key, value in params.items():
                url += f"&{key}={value}"
    
        try:
            if method == "GET":
                response = await self.client.get(url, headers=headers)
            else:
                response = await self.client.request(
                    method, url, headers=headers, json=json_data
                )
    
            if response.status_code != 200:
                error_text = response.text
                logger.error(f"API error {response.status_code}: {error_text}")
                raise Exception(f"API error {response.status_code}: {error_text}")
    
            data = response.json()
    
            # Handle OData response format
            if "d" in data:
                return data["d"]
            return data
    
        except httpx.TimeoutException:
            logger.error(f"Request timeout for {endpoint}")
            raise Exception("Request timed out")
        except Exception as e:
            logger.error(f"Request failed: {str(e)}")
            raise
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Get traffic statistics' implies a read-only operation, but it doesn't specify what 'top pages' means (ranking criteria, time period, or limit), whether authentication is required, or how results are structured. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just 6 words, front-loading the core purpose without any wasted words. Every element ('Get', 'traffic statistics', 'for top pages') contributes essential information, making it efficiently structured.

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 has an output schema (which handles return values) and only one parameter, the description's brevity is somewhat acceptable. However, with no annotations and 0% schema coverage, the description should provide more context about what 'top pages' means and the tool's behavioral characteristics to be truly complete.

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?

With 0% schema description coverage for the single parameter 'site_url', the description provides no additional parameter information. It doesn't explain what format the site_url should take, whether it needs to be a full URL or domain, or any validation requirements. The description fails to compensate for the complete lack of schema 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 action ('Get traffic statistics') and resource ('for top pages'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'get_url_traffic_info' or 'get_query_traffic_stats', which appear to offer similar traffic-related functionality.

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 multiple traffic-related sibling tools (get_url_traffic_info, get_query_traffic_stats, get_rank_and_traffic_stats), the agent receives no indication of what makes this tool distinct or when it's the appropriate choice.

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/isiahw1/mcp-server-bing-webmaster'

If you have feedback or need assistance with the MCP directory API, please join our Discord server