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.

Input Schema

TableJSON 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

TableJSON 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.4/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial operational detail beyond them: HEAD requests, low concurrency, robots.txt skip rules for Agent Tools, a cap of 46 requests and ~40 sampled addresses, sitemap-index priority order, and host-only scope. Return format is delegated to the output schema, which is appropriate.

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?

Front-loaded with purpose, then usage/examples, then behavior, then exclusions — a logical order where each clause carries information. It is dense and slightly long, but no sentence is redundant with the schema or annotations.

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?

Given an output schema exists, the description need not explain return values, and it covers everything else an agent needs: sampling limits, request budget, robots.txt behavior, host restriction, and unsupported use cases.

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% and the single 'domain' param is fully documented in the schema, including the 'pass a page address, only host is used' behavior. The description's 'Pass the domain' adds no meaning beyond that, so this is the baseline 3.

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+resource+scope: 'Finds broken or redirected pages in a sitemap sample.' This clearly differentiates it from siblings like trace_redirects (single redirect chain) and check_page_tags (content-level checks).

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?

Provides explicit trigger conditions with three natural-language example queries ('are any pages of shop.example.com broken?'), plus hard exclusions: private/local addresses, reading page content, and ongoing monitoring. Usage is unambiguous.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.