Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_crawl_stats

Fetch daily crawl statistics for a site within a date range. Supports pagination to access up to 500 rows per request.

Instructions

Retrieve crawl statistics for a specific site within a date range.

Args: site_url: The URL of the site

Returns: List[CrawlStats]: List of daily crawl statistics

Raises: BingWebmasterError: If statistics cannot be retrieved

Returns at most limit rows (default 50, max 500). When the result reports a next_offset, call again with offset=next_offset to get more rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of rows to return.
offsetNoIndex of the first row.
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "description": "Maximum number of rows to return.",
+  "maximum": 500,
+  "minimum": 1,
+  "title": "Limit",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Index of the first row.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}
    • removedInput schema / properties / self
      Removed value: -{
-  "title": "self",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "self",
-  "site_url"
-]New value: +[
+  "site_url"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "CrawlStats": {
+      "properties": {
+        "AllOtherCodes": {
+          "title": "Allothercodes",
+          "type": "integer"
+        },
+        "BlockedByRobotsTxt": {
+          "title": "Blockedbyrobotstxt",
+          "type": "integer"
+        },
+        "Code2xx": {
+          "title": "Code2Xx",
+          "type": "integer"
+        },
+        "Code301": {
+          "title": "Code301",
+          "type": "integer"
+        },
+        "Code302": {
+          "title": "Code302",
+          "type": "integer"
+        },
+        "Code4xx": {
+          "title": "Code4Xx",
+          "type": "integer"
+        },
+        "Code5xx": {
+          "title": "Code5Xx",
+          "type": "integer"
+        },
+        "ContainsMalware": {
+          "title": "Containsmalware",
+          "type": "integer"
+        },
+        "CrawlErrors": {
+          "title": "Crawlerrors",
+          "type": "integer"
+        },
+        "CrawledPages": {
+          "title": "Crawledpages",
+          "type": "integer"
+        },
+        "Date": {
+          "format": "date-time",
+          "title": "Date",
+          "type": "string"
+        },
+        "InIndex": {
+          "title": "Inindex",
+          "type": "integer"
+        },
+        "InLinks": {
+          "title": "Inlinks",
+          "type": "integer"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "AllOtherCodes",
+        "BlockedByRobotsTxt",
+        "Code2xx",
+        "Code301",
+        "Code302",
+        "Code4xx",
+        "Code5xx",
+        "ContainsMalware",
+        "CrawlErrors",
+        "CrawledPages",
+        "Date",
+        "InIndex",
+        "InLinks"
+      ],
+      "title": "CrawlStats",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/CrawlStats"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_crawl_statsOutput",
+  "type": "object"
+}
  3. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Without annotations, the description must carry behavioral disclosure. It does disclose return type, the BingWebmasterError, and the next_offset pagination loop, which are valuable. However, it claims the tool retrieves stats 'within a date range' while the schema provides no date-range parameters, so the agent is misled about an apparently core capability.

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?

The description is front-loaded with the purpose and uses a conventional Args/Returns/Raises structure. The pagination sentence is useful, though it partially repeats schema-provided default/max values; overall it's tight.

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

Completeness2/5

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

The output schema and error/pagination disclosures cover much of the return behavior, but the date-range capability promised in the first line has no corresponding parameters, leaving a critical gap in how to invoke the tool for that stated scope. There is also no guidance on how site_url is validated or whether any auth is needed, despite annotations being absent.

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?

The schema already describes limit and offset (67% coverage), so the description doesn't need to re-explain them; it adds value by spelling out the next_offset pagination pattern. But site_url only gets a trivial gloss ('The URL of the site') and the unsupported date-range assertion adds confusion rather than semantic detail.

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 states a specific verb ('Retrieve') and resource ('crawl statistics') for a specific site, and the resource name distinguishes it from sibling tools like get_crawl_settings and get_crawl_issues. However, the clause 'within a date range' is unsupported by the input schema, which lacks date parameters, adding ambiguity to the actual scope.

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?

It gives clear operational guidance about pagination (limit/offset/next_offset), but it does not state when to choose this over sibling tools or any exclusions. Usage context is implied ('crawl statistics' vs settings/issues) rather than explicitly routing the agent.

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

Deploy Server

Other Tools