Skip to main content
Glama

Site link health

site_link_health
Read-only

Pro. Check the links on a site. Crawls the site from url (same origin only, up to 40 pages, 4 requests at a time, or only the paths you list), uses sitemap.xml to find pages, and obeys robots.txt for the user agent ATPDesigners. Reads static HTML only. The result opens with coverage: pages read of pages found, which were skipped or truncated, and requests used. Collects internal links from the pages read, requests up to 60 destinations not already crawled (HEAD first, GET if HEAD fails), and reports non-2xx results, redirects (final URL only; hop counts are not visible), links to http, links with no name, vague link text, one text pointing to different places, and links with no destination. Links with aria-hidden=true are not counted as unnamed. Optional maxLinkChecks lowers the check cap.

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": "site_link_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesHome page or any page on the site. The crawl stays on this origin.
pathsNoOptional list of same-origin paths such as /about. When given, only these pages are read and links are not followed.
sitemapNoUse sitemap.xml to find pages. Default true.
maxPagesNoOptional lower page cap. The hard cap is 40 pages.
maxLinkChecksNoOptional lower cap on extra link requests. The hard cap is 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes far beyond the readOnly/openWorld annotations: concurrency (4 requests at a time), hard caps (40 pages, 60 destinations), robots.txt obedience with a named user agent, sitemap.xml usage, static-HTML-only limitation, HEAD-then-GET fallback, and the explicit caveat that redirect hop counts are not visible. It also states that aria-hidden links are exempt from the unnamed-link rule, which is exactly the kind of judgment call an agent needs to interpret output.

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?

Purpose is front-loaded in the first sentence and the rest is dense, non-redundant operational detail. Slightly over-packed for a single paragraph (the leading 'Pro.' token and the tail parameter note could be trimmed), but nearly every clause carries information.

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?

With no output schema, the description takes on the burden of describing the return value and does so: the result opens with a coverage block (pages read vs found, skips, truncations, requests used) followed by categorized link findings. Combined with the documented caps, an agent knows both what it will get back and what the crawl will and won't cover.

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 baseline is 3. The description restates the same facts the schema already carries — `paths` bypasses link following, `maxLinkChecks` 'lowers the check cap', `sitemap` being used to find pages — without adding format, syntax or interaction detail beyond the schema.

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 ('check the links on a site') and immediately scopes it: crawl same-origin, up to 40 pages, internal links only, 60 destination checks. Among the many site_* / audit_* siblings, link-health checking is clearly a distinct operation, and the enumerated finding types (non-2xx, redirects, http links, unnamed/vague link text) pin the purpose down further.

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 the mechanics rather than stated: the reader can infer this is a link-audit pass, and the `paths` mode ('only these pages are read and links are not followed') describes a distinct sub-use-case. However, no sibling is named and there is no explicit when-to-use / when-not guidance versus site_meta_audit, site_inventory or audit_site_accessibility.

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