Trace a 301 redirect chain
trace_redirectsTraces 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.
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": "trace_redirects"
}
}Input 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
| Name | Required | Description | Default |
|---|---|---|---|
| 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. |