Skip to main content
Glama

bing_get_crawl_stats

Retrieve Bing crawl statistics for a site to monitor pages crawled, errors, and index status over time.

Instructions

Get crawl statistics for a site from Bing. Shows pages crawled, errors, and index status over time.

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_crawl_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden; it does disclose the returned content (crawled pages, errors, index status over time), which is real added value. However, it omits the read-only nature, the time window that "over time" covers, whether a date range can be requested, and any pagination or rate-limit behavior.

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 short sentences with the purpose front-loaded and the second sentence spent on the useful payload enumeration. No filler, though the opening could have merged purpose and contents into one tighter sentence.

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 single-parameter read tool with no output schema, describing the returned metrics is the key completeness requirement and it is met. The remaining gap is the unspecified reporting window behind "over time," which matters because no date parameter exists to control it.

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 coverage is 100% for the single siteUrl parameter, so the schema already documents it fully. The description adds only the framing "for a site" and gives no format expectations (e.g., whether a scheme or subdomain is required) 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?

States a specific verb and resource ("Get crawl statistics for a site from Bing") and enumerates the contents (pages crawled, errors, index status). It does not distinguish itself from close siblings like bing_get_crawl_issues or bing_get_page_stats, so it stops short of a 5.

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 only implied by the phrase "for a site," which signals a siteUrl is needed, and by the general notion of checking crawl health. There is no explicit when-to-use versus when-to-use-a-sibling guidance and no prerequisites mentioned.

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