Skip to main content
Glama

Trace a URL's full redirect chain hop by hop (up to 10)

redirects
Read-only

Trace a URL's full redirect chain hop by hop (up to 10): status code, Location and server for each hop, final URL, and loop detection. Useful for link unshortening and SEO migrations. Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag readOnlyHint and openWorldHint, and the description adds substantial context beyond them: a 10-hop ceiling, explicit output fields per hop, loop detection, a 1-3 s latency expectation, a 20 calls/day free quota, and x402 USDC-per-call pricing above that. Only the failure/error behavior on unreachable URLs or blocked hosts is left unstated.

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 the core action and returned fields, followed by use cases, latency, and pricing. Every sentence carries information, though the pricing clause is dense and could be tightened without loss.

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 two-parameter read-only tool with no output schema, the description covers scope, output shape, hop limit, latency, quota, and cost. Nothing an agent needs to invoke it correctly is missing.

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% and the schema already documents both 'url' (public http(s) URL) and the x402 'payment' signature including the omitted-on-first-call flow. The description adds no further parameter meaning beyond that, so the 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 ('Trace a URL's full redirect chain hop by hop') and enumerates the returned fields (status code, Location, server, final URL, loop detection), plus a 10-hop cap. An agent can distinguish this from siblings like links, broken_links, or status without opening any schema.

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

Usage Guidelines3/5

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

Implies use cases ('link unshortening and SEO migrations') but never states when to choose this over the sibling tools such as links or broken_links, nor any exclusions. Usage context is present but left for the agent to infer.

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.