Skip to main content
Glama

Check the links on a web page for broken ones

broken_links
Read-only

Check the links on a web page for broken ones: requests up to 40 unique links in parallel and reports each status code, broken links (4xx/5xx/unreachable) and redirects. Takes 2-10 s. Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.005 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": "broken_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
limitNoMax links to check (1-40, default 40)
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.1/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses concurrency behavior (parallel requests, deduplicated to unique links), runtime range, classification of failures, and both rate limits (20 calls/day free) and overage pricing with the payment rail. These are precisely the operational facts an agent needs before calling, and none of them are recoverable from the annotations or schema.

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?

Three tightly packed sentences with the core action front-loaded and no filler; the cost sentence is justified because it changes agent behavior. It is dense but never redundant, though the pricing detail could be trimmed slightly against the fully documented payment parameter.

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?

There is no output schema, so the description carries the return-value burden and does — naming status codes, broken-link categories, and redirect reporting. Combined with latency, quota, and pricing disclosure for a 3-parameter tool, an agent has everything needed to decide and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3; the description still adds value by clarifying that 'limit' counts unique links and that the free threshold determines whether the 'payment' parameter is needed. The payment mechanics themselves are left to the schema, which documents them thoroughly.

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 states a specific verb and resource — fetching a page's links and checking each for breakage — plus the exact output shape (status codes, 4xx/5xx/unreachable, redirects) and the scale cap (up to 40 unique links). It is clearly distinct in purpose from generic extraction siblings like 'links' or 'redirects', though it never names those alternatives to draw the boundary explicitly.

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 only implied: the agent can infer this is the validation step after listing links, and the latency note (2-10 s) plus the free-tier quota help it decide whether a call is affordable. There is no explicit 'use this instead of links/redirects when…' guidance and no stated preconditions beyond the schema's requirement of a public http(s) URL.

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.