mcp-toolbelt

broken_link_check

Find broken links two ways. Default (crawl mode): crawl a site starting from a URL (same-origin pages only, bounded by maxPages) and check every linked URL for broken status codes, returning each broken link with the page(s) it was found on. Sitemap mode (viaSitemap: true): parse the site's sitemap.xml (following one level of sitemap-index nesting) and check the status of every URL listed in it instead. Note: some external sites (e.g. social platforms) block automated HEAD/GET requests and may show up as false positives.

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": {
      "url": "<url>"
    },
    "name": "broken_link_check"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Starting URL to crawl — or, in sitemap mode, the sitemap.xml URL or any page URL on the site
`maxPages`	No	Max same-origin pages to crawl in crawl mode (default 20, capped at 50)
`viaSitemap`	No	Check the URLs listed in the site's sitemap.xml instead of crawling pages (default false)
`checkExternal`	No	Crawl mode only: also check links pointing off-site (default true; crawling never follows off-site links)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 21, 2026

changedInput schema / properties / checkExternal / description

Previous value: -"Also check links pointing off-site (default true; crawling never follows off-site links)"New value: +"Crawl mode only: also check links pointing off-site (default true; crawling never follows off-site links)"

changedInput schema / properties / maxPages / description

Previous value: -"Max same-origin pages to crawl (default 20, capped at 50)"New value: +"Max same-origin pages to crawl in crawl mode (default 20, capped at 50)"

changedInput schema / properties / url / description

Previous value: -"Starting URL to crawl"New value: +"Starting URL to crawl — or, in sitemap mode, the sitemap.xml URL or any page URL on the site"

addedInput schema / properties / viaSitemap

Added value: +{
+  "description": "Check the URLs listed in the site's sitemap.xml instead of crawling pages (default false)",
+  "type": "boolean"
+}

First observedAug 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses same-origin crawling, maxPages bounds, one-level sitemap-index nesting, that crawling never follows off-site links, and that some external sites may produce false positives due to blocked automated requests. It does not mention timeouts or rate limits, but the behavioral disclosure is substantial.

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 front-loaded with the core purpose, then explains the default mode, the sitemap mode, and a relevant false-positive caveat. Every sentence adds useful information with no filler.

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 annotations and no output schema, the description does a good job covering modes, scoping, and return behavior for crawl mode. Sitemap-mode return semantics are slightly less explicit, and runtime details like timeouts are omitted, but the definition is close to complete for an agent to invoke it correctly.

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 description coverage is 100%, so the schema already documents all four parameters. The description adds useful mode context for url, maxPages, and viaSitemap, but does not add meaning for checkExternal beyond what the schema already states. Baseline 3 applies.

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?

States a specific verb and resource: find broken links. It clearly describes two operating modes, crawl mode and sitemap mode, which lets an agent distinguish this from sibling tools like redirect_chain_check or check_robots_sitemap.

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?

Explains the default crawl mode and the sitemap mode trigger viaSitemap: true, giving clear context for when each mode applies. It does not explicitly compare against sibling tools or state when not to use this tool, but the mode selection guidance is strong.

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

All mcp-toolbelt tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?