Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Crawl Stats

bing_webmaster_get_crawl_stats
Read-only

Retrieve Bingbot crawl stats for a site and date window, including pages crawled, crawl errors, status classes, robots.txt blocks, malware, DNS failures, timeouts, index pages, and inbound links.

Instructions

How Bingbot crawled the site over a date window: pages crawled, crawl errors, responses by status class (2xx, 301, 302, 4xx, 5xx), robots.txt blocks, malware, DNS failures and timeouts, summed over the window; plus pages in the index and inbound links as first/last values (those are levels, not counters). Bing keeps about six months of daily rows and returns them all in one call; this tool filters them.

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_crawl_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.
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.
include_seriesNoAlso return one row per day in the window. Defaults to false (totals only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the readOnly/openWorld annotations by disclosing that Bing retains roughly six months of daily rows and returns the entire history in one call, which this server then filters. It also flags the crucial aggregation semantics – counters summed over the window versus index pages and inbound links reported as first/last levels, not counters – which prevents misreading the response.

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?

Two sentences, front-loaded with the core purpose and the metric inventory follows immediately. The first sentence is dense with lists but every item carries information; no filler or restatement of the name.

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

Completeness5/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 so fully: what is summed, what is reported as first/last levels, and how much history exists. An agent can call this correctly and interpret the result without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds value by explaining why the range is cheap to widen ('returns them all in one call; this tool filters them') and by reinforcing that the window governs the summation. It does not add detail on include_series beyond what the schema already says.

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?

States a specific verb and resource ('How Bingbot crawled the site over a date window') and enumerates exactly which counters are returned (pages crawled, errors by status class, robots.txt blocks, malware, DNS failures, timeouts). This clearly separates it from issue-listing or page-level siblings, but it never names an adjacent tool, so the agent must infer routing from the vocabulary alone.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: reach for this when you want aggregated crawl behavior over a date window. There is no explicit when-not-to-use or pointer to alternatives such as crawl issues or link counts, even though index pages and inbound links appear here too and could plausibly overlap with a link-count tool.

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