Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Crawl Issues

bing_webmaster_get_crawl_issues
Read-only

Retrieve a site's Bing Webmaster crawl issues by type, then list affected URLs most-linked first; filter by issue and cap results to diagnose and fix crawl errors.

Instructions

The site's URLs with crawl problems, counted by issue type (Code4xx, Code5xx, Code301, Code302, BlockedByRobotsTxt, ImportantUrlBlockedByRobotsTxt, ContainsMalware, DnsErrors, TimeOutErrors), then the URLs themselves, most-linked first, capped by limit. A fixed issue can take a few days to drop off Bing's list.

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

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.
issueNoKeep only URLs with this issue, e.g. "Code4xx". The counts still cover every URL.
limitNoMaximum URLs to return (1-500). Defaults to 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description still adds substantive behavior: result ordering is most-linked first, output is capped by limit, and stale issues linger for a few days after being fixed. That last point is exactly the kind of latency caveat an agent needs to avoid re-reporting resolved errors.

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 dense sentences with no filler; the return shape is front-loaded and the freshness caveat is placed last where it belongs. Every clause carries information.

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?

With no output schema, the description carries the burden of describing the response, and it does so at the structural level (counts by issue type, then URLs ordered most-linked first). It does not say what per-URL fields appear, but an agent has enough to call it and interpret the shape.

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%, so the baseline is 3; the schema already documents site matching, the issue enum, and the 1-500 limit range. The description adds only the ordering semantics of limit's cap and restates the issue type list already present as an enum, so it does not meaningfully exceed 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?

The description names a specific resource (the site's URLs with crawl problems) and states exactly what comes back: per-issue-type counts followed by the URLs themselves. It is not explicitly differentiated from the neighboring bing_webmaster_get_crawl_stats, which an agent could plausibly confuse it with, 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 purpose statement — find URLs with crawl problems for a site, optionally narrowed by the issue filter. There is no explicit when-to-use/when-not framing and no mention of the crawl-stats sibling as the counts-only alternative. The staleness note is a caveat, not routing guidance.

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