Skip to main content
Glama

Check links

check_links
Read-onlyIdempotent

Check a list of URLs to find working, broken, and redirected links, showing final destinations and HTTP status codes. Use it to clean up docs, READMEs, sitemaps, or bookmarks.

Instructions

Check web links and follow their redirects.

Use this when you have a list of URLs and need to know which ones work, which are broken (404, 500, timeouts, bad hosts) and where redirects end up, for example to clean up docs, a README, a sitemap list or bookmarks. It does not crawl a site or read page content; pass the exact links you want checked. Links that are not http or https come back with ok false and an error.

urls: up to 200 http(s) links. timeout: seconds to wait for each link.

Returns one result per link: {url, status, ok, final_url, redirects, error}. status is the HTTP code of the last hop (null if it could not connect). ok is true for 200-399. redirects lists each hop as "CODE url".

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": {
      "urls": "<urls>"
    },
    "name": "check_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
timeoutNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description adds substantial context on top: a 200-link cap, the treatment of non-http(s) inputs (ok false plus an error), and the meaning of ok (200-399) versus status (null when connection fails). This is behavioral detail the annotations cannot convey.

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?

The text is front-loaded, moving from purpose to scope to parameters to return shape in four tight blocks with no filler. The 'Returns one result per link' block partially restates what the output schema already declares, a small redundancy, but it earns its place by defining the ok/status semantics.

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 network tool with an output schema, the description covers the gaps that matter: input limits, invalid-scheme handling, per-hop redirect format, and status/ok semantics. Nothing an agent needs to invoke it correctly or interpret edge cases is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the load, and it does: 'up to 200 http(s) links' imposes a cap and scheme restriction absent from the schema, and 'timeout: seconds to wait for each link' clarifies that the value is per-link rather than for the whole batch. Both parameters gain meaning the schema does not provide.

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?

The opening sentence pairs a specific verb and resource ('Check web links and follow their redirects') and then explicitly draws the boundary that separates it from content-oriented siblings: 'It does not crawl a site or read page content.' An agent can distinguish it from convert_to_markdown or extract_pdf_tables without inspecting 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 Guidelines4/5

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

The description gives a concrete when-to-use trigger ('when you have a list of URLs and need to know which ones work...broken...where redirects end up') with example scenarios, plus an explicit when-not ('does not crawl a site'). No sibling alternative is named by name, so it falls just short of the full when/when-not/alternatives bar.

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