Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Page Stats

bing_webmaster_get_page_stats
Read-only

Retrieve Bing Webmaster page performance for a site over a date window, including clicks, impressions, CTR, and average position, with filtering and sorting for analysis.

Instructions

The site's pages that appeared in Bing search over a date window, each with clicks, impressions, CTR and average position. Bing only reports its top pages. For the queries behind one page, use bing_webmaster_get_page_queries. Bing updates this weekly. Bing has no date parameter on this method: one call returns the site's whole history, which this tool filters to the window, aggregates per key, sorts and cuts. Calling it again with another window costs the same single call.

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": {
      "site": "<site>"
    },
    "name": "bing_webmaster_get_page_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site, e.g. "example.com" or "https://www.example.com/". Matched against the sites this API key reaches (bing_webmaster_list_sites), tolerating a missing scheme, www. or trailing slash; an ambiguous or unknown site is refused with the list of accessible ones.
limitNoMaximum pages to return (1-1000). Defaults to 50.
sort_byNoSort order, best first: clicks, impressions, ctr (highest first — noisy on keys with few impressions), or position (lowest, i.e. best, average position first). Defaults to clicks.clicks
containsNoKeep only page URLs containing this text (case-insensitive), e.g. "pricing".
end_dateNoLast day of the window, inclusive, YYYY-MM-DD. Defaults to today (UTC). Bing's search data lags a few days and is bucketed (often weekly), so the newest days are usually empty.
start_dateNoFirst day of the window, inclusive, YYYY-MM-DD. Defaults to 28 days before end_date. Bing returns the whole history and this server filters it, so any range Bing still holds works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint: it warns that Bing only reports its top pages (a truncation caveat the agent cannot learn from the schema), that data is updated weekly and therefore stale at the edges, and that the underlying API takes no date parameter, so the server fetches all history and filters/aggregates/sorts/cuts locally. That last point materially changes how an agent should think about call cost and unusual ranges.

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?

Front-loads what is returned and then layers the caveats in short, high-density sentences with no filler. The final sentence restates the fetch-all-then-filter model already established one sentence earlier, which is the only real redundancy.

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?

With no output schema, the description carries the return-shape burden and does name the returned metrics, which is the critical part. It leaves one question open: how metrics across the window are aggregated per page (summed clicks vs. averaged position/CTR), which matters for interpreting rankings but is not spelled out.

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%, so every parameter including site, limit, sort_by, contains, start_date and end_date is already documented with defaults, ranges and format. The description adds only the general notion of a 'window' and per-key aggregation, not any parameter syntax or behavior the schema lacks. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with the exact resource returned (pages appearing in Bing search) and enumerates the metrics (clicks, impressions, CTR, average position) plus the date-window scope. It explicitly distinguishes itself from bing_webmaster_get_page_queries, so an agent can choose between the page-level and query-level views without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative (get_page_queries) and the exact condition that selects it (the queries behind one page). It also gives a decision rule for window size — another call with a different window costs the same single fetch — which is the main usage judgment this tool requires.

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