Site SEO & AI Crawler Audit

Check a sitemap sample for broken links

link_sample_check

Read-onlyIdempotent

Finds broken or redirected pages in a sitemap sample. Use it when the user asks whether pages of an online store or website are broken or redirected, or for a broken link in the sitemap, for example "are any pages of shop.example.com broken?", "check my sitemap for 404s" or "do my product pages redirect?". Pass the domain. Reads the sitemap (for a sitemap index, the product, page, collection and blog sitemaps first) and checks up to 40 addresses spread across it, on that host only, returning counts by status, and for each broken, unreachable or redirected address its status and final address. It is a sample, not every page; it uses HEAD requests at low concurrency, skips addresses that robots.txt disallows for Agent Tools, and makes at most 46 requests. Do not use it for private or local addresses, to read page content, or to monitor a site over time.

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": {
      "domain": "<domain>"
    },
    "name": "link_sample_check"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Host name of a public store or website, for example shop.example.com. If you only have a page address, pass it: only its host is used.

Output Schema

Name	Required	Description
`notes`	No	Plain-language caveats to pass on with the result.
`domain`	Yes	Host checked.
`issues`	No
`notice`	Yes	As-of caveat: what the site sent to Agent Tools at that moment, not what every agent sees.
`origin`	No	Origin the sitemap was read from, after redirects.
`robots`	No
`source`	Yes	Where the data came from: the website itself.
`failure`	No	Why the site or page was not reached or read, such as a timeout or a robots.txt disallow for Agent Tools.
`sitemap`	No
`summary`	No	Counts for the sample of up to 40 addresses.
`statuses`	No	Count of sampled addresses for each HTTP status code.
`reachable`	Yes	False when the site did not answer; failure then says why.
`requestsMade`	No	Requests made, at most 46.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedOct 12, 2026

changedInput schema / properties / domain / description

Previous value: -"Domain of a public store or website, for example shop.example.com. Only the host is used. A full address is accepted and reduced to its host."New value: +"Host name of a public store or website, for example shop.example.com. If you only have a page address, pass it: only its host is used."

addedOutput schema / properties / domain / description
```
Added value: +"Host checked."
```

addedOutput schema / properties / failure / description

Added value: +"Why the site or page was not reached or read, such as a timeout or a robots.txt disallow for Agent Tools."

addedOutput schema / properties / notes / description

Added value: +"Plain-language caveats to pass on with the result."

addedOutput schema / properties / notice / description

Added value: +"As-of caveat: what the site sent to Agent Tools at that moment, not what every agent sees."

addedOutput schema / properties / origin / description

Added value: +"Origin the sitemap was read from, after redirects."

addedOutput schema / properties / reachable / description

Added value: +"False when the site did not answer; failure then says why."

addedOutput schema / properties / requestsMade / description
```
Added value: +"Requests made, at most 46."
```
addedOutput schema / properties / robots / properties / httpStatus / description
```
Added value: +"HTTP status code of robots.txt."
```
addedOutput schema / properties / robots / properties / sitemaps / description
```
Added value: +"Sitemap addresses listed in robots.txt."
```

addedOutput schema / properties / robots / properties / status / description

Added value: +"found: rules were read. missing: a 4xx answer, so nothing is restricted. unreachable: a 5xx or no answer, so no other file or page was requested."

addedOutput schema / properties / sitemap / properties / found / description
```
Added value: +"False when no sitemap was found, so nothing was sampled."
```
addedOutput schema / properties / sitemap / properties / kind / description
```
Added value: +"index for a sitemap index, otherwise urlset."
```
addedOutput schema / properties / sitemap / properties / truncated / description
```
Added value: +"True when the sitemap was too large to read in full."
```
addedOutput schema / properties / sitemap / properties / url / description
```
Added value: +"Address of the sitemap read."
```
addedOutput schema / properties / sitemap / properties / urlsListed / description
```
Added value: +"Addresses listed in the sitemaps read."
```

addedOutput schema / properties / source / description

Added value: +"Where the data came from: the website itself."

addedOutput schema / properties / statuses / description

Added value: +"Count of sampled addresses for each HTTP status code."

addedOutput schema / properties / summary / description

Added value: +"Counts for the sample of up to 40 addresses."

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With annotations already covering read-only, idempotent and open-world traits, the description goes substantially beyond them: it discloses the sampling cap (up to 40 addresses), request ceiling (46), HEAD method, low concurrency, robots.txt skipping for its own user agent, host restriction, and the sitemap-index traversal order. The only notable omission is how partial failures or an unreachable sitemap surface, which the output schema largely covers.

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?

Purpose and trigger examples are front-loaded, followed by behavioural detail and then exclusions — a sensible ordering. The three inline quoted user phrasings are somewhat verbose and could be trimmed, but each still demonstrates a distinct intent.

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?

For a tool with an output schema and rich annotations, the description covers everything an agent needs to decide and invoke: scope, sample limits, network cost, politeness constraints, and boundaries. Nothing material is left to inference.

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?

Only a single parameter exists and its schema description is fully documented, including the host-extraction behaviour, so the description's "Pass the domain" adds little beyond the schema. It correctly reinforces the one non-obvious rule (host-only scoping) but does not otherwise extend parameter meaning.

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?

"Finds broken or redirected pages in a sitemap sample" pairs a specific verb with a specific resource and states the sampling scope up front. An agent can distinguish this from a single-URL crawler like trace_redirects or a landing_page_check without opening the schema.

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

Usage Guidelines5/5

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

The description gives trigger conditions (user asks whether site pages are broken/redirected) with three concrete example phrasings, and then explicit exclusions: no private/local addresses, not for reading page content, not for ongoing monitoring. This is the when/when-not/alternative pattern in full.

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

All Site SEO & AI Crawler Audit tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.