Skip to main content
Glama
Sign In
mcp-server-bwt

mcp-server-bwt

by agalliani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_crawl_issues

Identify URLs that Bing's crawler had trouble accessing or processing, helping you detect and fix crawl issues for a specific 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

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_url": "<site_url>"
    },
    "name": "get_crawl_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, but the description documents the return type and a BingWebmasterError failure mode, and the 'get' name implies read-only. It doesn't disclose permissions, rate limits, or whether the site must be verified, leaving the safety profile partly implicit.

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 compact and uses a clear Args/Returns/Raises structure with the main purpose front-loaded. The 'This helps identify...' sentence is useful but slightly overlapping with the first sentence, so it isn't flawless.

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-only tool with an output schema, the description covers purpose, argument, return, and error behavior. It is missing only richer site_url constraints and alternative-tool routing, which are minor at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameter semantics, but the Args section only restates the schema ('site_url: The URL of the site') without adding format, verification requirements, or an example. The parameter is simple, but no extra meaning is added.

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 opening sentence states a precise action and resource: 'Get a list of URLs with crawl issues for a specific site.' The second sentence clarifies the value ('pages that Bing's crawler had trouble accessing or processing') and distinguishes it from sibling tools like get_crawl_stats and 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 a clear use case: use it to identify pages that Bing's crawler had trouble accessing or processing. It does not mention exclusions or name a sibling alternative, so it falls short of explicit when-not-to-use guidance.

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