Skip to main content
Glama

Trace a URL's redirect chain hop by hop

redirects
Read-only

The redirect chain of a URL, hop by hop (at most 10 hops): each URL, its status, the Location it points to, and whether the hop goes from http to https or changes host. Returns the final URL and status, total hops, loop true when a URL repeats, and the Strict-Transport-Security header of the final response. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "redirects"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL or domain, e.g. example.com

Output Schema

NameRequiredDescriptionDefault
urlNo
hopsNo
hstsNo
loopNo
maxHopsNo
finalUrlNo
checkedAtNo
totalHopsNo
truncatedNo
finalStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checkedAt": {},
      +    "finalStatus": {},
      +    "finalUrl": {},
      +    "hops": {},
      +    "hsts": {},
      +    "loop": {},
      +    "maxHops": {},
      +    "totalHops": {},
      +    "truncated": {},
      +    "url": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds real value with the 10-hop cap, loop detection via a repeated URL, HSTS header of the final response, and x402 payment terms plus the fact that failed calls are not charged. However, the pricing sentence is a single unpunctuated run-on clause that requires careful parsing, and it says nothing about behavior on errors or timeouts. Useful but not fully disclosed.

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?

It front-loads the resource and its output fields, then adds scope limits and price — every fact earns its place. The dense, run-on pricing clause could be split for faster scanning.

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, yet the description independently summarizes the return shape (final URL, status, total hops, loop flag, HSTS), and it covers the cost model and hop limit an agent needs before invoking. It falls just short by not addressing failure or timeout behavior for a network-dependent tool.

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?

There is one parameter with 100% schema description coverage ('Page URL or domain, e.g. example.com'), so the schema does the heavy lifting. The description adds no syntax or format meaning beyond that, which is the expected baseline when coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource — a URL's redirect chain — and enumerates what each hop contains (URL, status, Location, scheme/host change), so an agent knows exactly what operation it is selecting. It lacks an explicit verb like 'trace' or 'fetch' (the title carries that), and it does not name sibling tools, but no sibling plausibly overlaps.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives, no prerequisites, and no exclusions. The only implicit cue is that it operates on a URL, which the schema already tells the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources