Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_crawl_issues

Identify URLs that Bing's crawler failed to access or process, returning a paginated list of crawl issues for a site.

Instructions

Get a list of URLs with crawl issues for a specific site.

This helps identify pages that Bing's crawler had trouble accessing or processing.

Args: site_url: The URL of the site

Returns: List[UrlWithCrawlIssues]: List of URLs with their associated crawl issues

Raises: BingWebmasterError: If issues 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": {
+    "CrawlIssues": {
+      "enum": [
+        16,
+        1,
+        2,
+        4,
+        8,
+        32,
+        128,
+        64,
+        0,
+        256
+      ],
+      "title": "CrawlIssues",
+      "type": "integer"
+    },
+    "UrlWithCrawlIssues": {
+      "properties": {
+        "HttpCode": {
+          "title": "Httpcode",
+          "type": "integer"
+        },
+        "InLinks": {
+          "title": "Inlinks",
+          "type": "integer"
+        },
+        "Issues": {
+          "$ref": "#/$defs/CrawlIssues"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "HttpCode",
+        "Issues",
+        "Url",
+        "InLinks"
+      ],
+      "title": "UrlWithCrawlIssues",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/UrlWithCrawlIssues"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_crawl_issuesOutput",
+  "type": "object"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses pagination behavior ('Returns at most limit rows... call again with offset=next_offset'), the default and maximum limit, and the error type raised. This goes beyond a simple description and helps the agent anticipate response handling.

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?

The description is well-structured and front-loaded with the core purpose. Each section (Args, Returns, Raises, pagination note) earns its place and adds useful information without repetition or filler.

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?

The description is complete for a tool of this complexity: it identifies the required parameter, explains pagination, notes the error type, and describes the return concept. With an output schema present, the description does not need to fully detail return fields, and nothing essential is missing for correct invocation.

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?

The input schema documents limit and offset with descriptions, but site_url lacks a schema description. The description compensates by specifying 'site_url: The URL of the site.' It also explains the relationship between limit, offset, and next_offset, adding meaning beyond the raw schema fields.

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?

The description clearly states a specific verb and resource: 'Get a list of URLs with crawl issues for a specific site.' It explains what the tool identifies (pages Bing's crawler had trouble accessing or processing), and this is distinct from sibling tools like get_crawl_stats or get_crawl_settings.

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

Usage Guidelines4/5

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

The description gives clear context on when to use the tool: to identify pages that Bing's crawler had trouble accessing or processing. It does not explicitly name alternative tools or state when not to use it, but the use case is clear enough for an agent to select it appropriately among siblings.

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