Skip to main content
Glama

Check every link on a page for broken ones

links
Read-only

Every link on one page (anchor text, internal or external) and a status check of up to 40 of them: status, final URL after redirects, ok, and the error for network failures. Totals: found, checked, broken, redirected and skipped beyond the 40. scope=all, internal or external. robots.txt is respected. Price: $0.003 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": "links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL or domain
scopeNoall (default), internal or external

Output Schema

NameRequiredDescriptionDefault
urlNo
noteNo
linksNo
scopeNo
totalsNo
finalUrlNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checkedAt": {},
      +    "finalUrl": {},
      +    "links": {},
      +    "note": {},
      +    "scope": {},
      +    "totals": {},
      +    "url": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description has to earn credit elsewhere and it does: it states the hard 40-link check cap, that robots.txt is respected, that redirects are followed and reported, and that the call costs $0.003 via x402 with failed calls uncharged. Billing and truncation behavior are exactly the non-obvious traits an agent needs, though rate limits and timeout behavior are 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?

A single dense paragraph that front-loads what is returned, then totals, then scope, then the operational caveats (robots, pricing). Nothing is filler, though the run-on structure listing returns and totals in one sentence makes it slightly harder to scan than a short bulleted layout would.

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?

Given that an output schema exists, the description need not define return fields, yet it still summarizes them briefly and spends its words on the things the schema cannot convey: the 40-check cap, skipped-link counting, robots.txt, redirect resolution, and the payment model. There is no gap an agent would trip over before calling it.

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%, so the schema already documents url and scope, and the description's 'internal or external' merely echoes the enum values. The one piece of added meaning is clarifying that url accepts either a full page URL or a bare domain, which goes slightly beyond the schema's 'Page URL or domain' wording. Baseline 3 is appropriate.

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?

Opens with a specific verb and resource: 'Every link on one page (anchor text, internal or external)' plus a status check of up to 40. An agent immediately knows this is a page-crawl link auditor, not a redirect tracer or site-wide crawler. It loses the top mark only because it never names the closest sibling (redirects) to explicitly separate the two.

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?

The 'one page' scope and the 40-link cap implicitly tell the agent this is a per-page tool, and robots.txt/pricing hints at when it is appropriate to call. But there is no explicit when-to-use or when-not guidance and no pointer to an alternative for multi-page crawls or for redirect chains specifically.

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