Skip to main content
Glama

BRAINIAC Technical SEO Audits

Analyse redirect chains and loops

seo-technical_redirect-chain-analyze
Read-onlyIdempotent

Walk caller-supplied redirect hops for chains, loops, mixed permanent/temporary statuses and HTTPS-to-HTTP downgrades. Price $0.02 USDC. POST /api/v1/seo-technical/redirect-chain-analyze. An unpaid call returns the x402 payment terms and does not run.

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": {
      "hops": "<hops>"
    },
    "name": "seo-technical_redirect-chain-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
hopsYeshops, array. Required.

Output Schema

NameRequiredDescriptionDefault
loopsNoloops. Array.
chainsNochains. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds important non-annotation context: the $0.02 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms without running. It does not cover rate limits or return shape, but an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences: main purpose is front-loaded, followed by price, endpoint, and unpaid-call behavior. Every sentence carries operational value with no filler.

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?

Strong completeness for a single-parameter analysis tool with an output schema: purpose, specific checks, payment requirement, endpoint, and unpaid-call behavior are all present. Minor operational details, such as whether any external fetch occurs despite openWorldHint, are absent but not essential.

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?

The single `hops` parameter is fully described in the schema, including nested from/to/status constraints and 100% description coverage. The description reinforces that hops are caller-supplied but adds no syntax or meaning beyond the schema, so the high-coverage baseline of 3 applies.

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?

States a specific verb and resource ('Walk caller-supplied redirect hops') and enumerates the checks performed: chains, loops, mixed permanent/temporary statuses, and HTTPS-to-HTTP downgrades. It does not explicitly name or contrast any sibling tool, so differentiation is implicit rather than stated.

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?

Usage is implied by 'caller-supplied redirect hops' and the listed analysis cases, but there is no explicit when-to-use/when-not guidance and no named alternative among the many seo-technical tools.

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