Skip to main content
Glama

bing_get_crawl_issues

Retrieve Bing crawl issues and errors for a site to identify problematic URLs, HTTP status codes, and issue types for troubleshooting and remediation.

Instructions

Get crawl issues/errors for a site from Bing. Shows URLs with problems, HTTP codes, and issue types.

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

Input Schema

NameRequiredDescriptionDefault
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the shape of the result (problem URLs, HTTP codes, issue types) and implicitly signals a read-only operation via 'Get', but it says nothing about volume limits, pagination, or whether results cover all issues or a recent window.

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?

Two short sentences, front-loaded with the action and resource, followed by the return content. Nothing is padded or redundant.

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 one-parameter read tool with no output schema and no annotations, the description covers purpose and return content adequately. Minor gaps remain around result limits, time window, and whether the site needs prior registration, but nothing essential to invoking it is missing.

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 defines the input. The description adds only the mild implication that the URL identifies the site to be inspected, without clarifying format (domain vs. full URL) or whether the site must already be registered via bing_list_sites.

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 concrete verb and resource ('Get crawl issues/errors for a site from Bing') and names the returned content, which is enough to separate it from bing_get_crawl_stats or bing_get_page_stats. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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?

The diagnostic intent of the tool is implied by 'issues/errors' and 'URLs with problems', so an agent can infer when to reach for it. There is no explicit when-to-use statement, no mention of the alternative stats tools, and no prerequisite or scoping guidance beyond the required site URL.

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