Site SEO & AI Crawler Audit

Trace a 301 redirect chain

trace_redirects

Read-onlyIdempotent

Traces the redirects and headers of a web address. Use it when the user asks where a web address redirects to, or for a 301 redirect chain, for example "why does http://example.com end up on another address?", "show the redirect chain for this link" or "does this site redirect http to https?". Pass the address. Returns each hop with its status code and target, the final address and status, whether http is upgraded to https, and the main response headers such as cache-control and strict-transport-security. At most 6 redirects are followed. Do not use it for private or local addresses, to read page content, or to scan a site for vulnerabilities.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Address of a public web page, for example https://example.com/pricing. A bare domain such as example.com means https. Only public http and https sites on the standard ports are checked.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The address checked, after a bare domain became https.
`chain`	Yes	Each hop in order, ending with the final page.
`notes`	No	Plain-language caveats to pass on with the result.
`notice`	Yes	As-of caveat: what the site sent to Agent Tools at that moment, not what every crawler sees.
`source`	Yes	Where the data came from: the website itself.
`status`	No	HTTP status code of the final page.
`failure`	No	Why the page was not reached or read, such as a timeout or a refused redirect.
`headers`	No	Main response headers of the final page, such as cache-control.
`finalUrl`	No	Address of the final page after redirects.
`reachable`	Yes	False when no page answered; failure then says why.
`upgradesToHttps`	No	True when an http address redirects to https.
`missingSecurityHeaders`	No	Common security headers the https page lacks.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 12, 2026

addedOutput schema / properties / chain / description

Added value: +"Each hop in order, ending with the final page."

addedOutput schema / properties / chain / items / properties / location / description
```
Added value: +"Location header of a redirect hop: where it points next."
```
addedOutput schema / properties / chain / items / properties / status / description
```
Added value: +"HTTP status code of this hop, such as 301 or 200."
```
addedOutput schema / properties / chain / items / properties / url / description
```
Added value: +"Address requested at this hop."
```

addedOutput schema / properties / failure / description

Added value: +"Why the page was not reached or read, such as a timeout or a refused redirect."

addedOutput schema / properties / finalUrl / description

Added value: +"Address of the final page after redirects."

addedOutput schema / properties / headers / description

Added value: +"Main response headers of the final page, such as cache-control."

addedOutput schema / properties / missingSecurityHeaders / description
```
Added value: +"Common security headers the https page lacks."
```

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 crawler sees."

addedOutput schema / properties / reachable / description

Added value: +"False when no page answered; failure then says why."

addedOutput schema / properties / source / description

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

addedOutput schema / properties / status / description

Added value: +"HTTP status code of the final page."

addedOutput schema / properties / upgradesToHttps / description

Added value: +"True when an http address redirects to https."

addedOutput schema / properties / url / description

Added value: +"The address checked, after a bare domain became https."

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.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's real additions are the 6-redirect follow cap and the public-only/standard-port restriction. It doesn't say what happens when the cap is exceeded or whether there is a timeout, which is a residual gap for a network-dependent trace.

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 is front-loaded in the first sentence, followed by triggers, return summary, and exclusions in a logical order. It is slightly long because of the multiple quoted user phrasings, but those quotes earn their place by disambiguating intent.

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?

An output schema exists (so return shape needn't be explained) and annotations cover safety, yet the description still usefully restates hops, final status, https upgrade, and headers. The only meaningful omission is behavior when the 6-redirect limit is hit (error vs. truncation).

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% with a single parameter, so the schema already documents the url format, bare-domain-as-https behavior, and public-site restriction. The description only says "Pass the address," adding nothing the schema doesn't already state, so 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 (traces redirects/headers of a web address) and the title narrows it to a 301 redirect chain. This is unmistakably distinct from siblings like check_page_tags, exposure_check, or ai_readiness_check, so an agent can select it without ambiguity.

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?

Gives explicit when-to-use triggers via three example user phrasings (where does this redirect, show the chain, does it upgrade http to https) and explicit when-not conditions (no private/local addresses, no page content reading, no vulnerability scanning). The alternative space is bounded even though siblings aren't named.

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.