Skip to main content
Glama

bing_get_page_stats

Retrieve page-level Bing statistics for a site, including impressions, clicks, and positions per page. Use weekly data to identify pages that attract traffic and where rankings can improve.

Instructions

Get page-level statistics for a site from Bing. Shows impressions, clicks, and positions per page. Data updates weekly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteUrl": "<siteUrl>"
    },
    "name": "bing_get_page_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the exact metrics returned (impressions, clicks, positions) and a weekly refresh cadence, which affects how fresh an agent should expect results to be. It omits auth requirements, whether a date range or history is available, result volume/pagination, and any rate limits, so meaningful gaps remain for a read tool with zero annotation coverage.

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?

Three short sentences, front-loaded with the core action, followed by what is returned and then the refresh cadence. No redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read tool with no output schema, the description covers the action, the returned metrics, and data freshness, which is enough to call it correctly. The main residual gap is the lack of any scoping or time-range detail for the siteUrl input.

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 100% for the single siteUrl parameter, so the schema already documents it. The description only reinforces that the statistics are scoped to a site and adds no format, normalization, or validation detail beyond the schema.

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?

"Get page-level statistics for a site from Bing" gives a specific verb (get) and resource (page-level statistics), and the phrase "per page" implicitly separates it from query-level and crawl-level siblings. It stops short of naming or contrasting those siblings, but an agent can still tell what this returns.

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?

There is no statement of when to choose this over bing_get_query_stats, bing_get_crawl_stats, or bing_get_traffic. Usage is only inferable from "for a site" and "per page"; no exclusions or preconditions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.