Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

Broken link checker

ayrank_broken_links
Read-only

Checks up to 100 links on one page and reports broken, redirect, denied, rate-limited, server-error, and timeout statuses so you can identify and fix broken links without a full site crawl.

Instructions

Use to find broken links on one page: AY Rank's server sends one GET to each of up to 100 links on it and reports ok, redirect, broken, denied, rate-limited, server-error, timeout and so on. Takes up to 25 s. Not a site crawl. Not for anchor text review (use ayrank_internal_links). Free AY Rank API, no key. JavaScript is not run, so content added by scripts is not seen.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe page whose links to check, like https://example.com/page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, external-call nature is covered structurally. The description still adds real context beyond that: one GET per link, a cap of 100 links, a ~25 s ceiling, the vocabulary of outcomes (ok/redirect/broken/denied/rate-limited/server-error/timeout), no key required, and that JavaScript is not executed. This is meaningful disclosure, but it stops short of saying how results are ordered or whether the 100-link cap truncates silently.

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?

Front-loaded with the action and scope, then the exclusions, then the operational traits. Sentences are short, declarative, and each carries a distinct fact; nothing is redundant with the name or title.

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 compensates by enumerating the reported status categories and disclosing duration, link cap, and the JavaScript limitation. For a single-parameter read tool that is enough for an agent to call it correctly and interpret the response class.

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% and there is only one parameter, so the schema already carries the semantics — baseline 3 applies. The description's 'one page' framing does reinforce that url is a page rather than a domain, but that is confirmation rather than new detail.

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 description opens with a specific verb and resource ('find broken links on one page') and immediately bounds scope ('Not a site crawl'), which separates it from a crawler sibling. It also names a distinct non-use ('Not for anchor text review') pointing to ayrank_internal_links, so an agent can pick it without opening 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 Guidelines5/5

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

Both directions are explicit: use it for per-page link verification, do not use it as a site crawl, and do not use it for anchor-text review — use ayrank_internal_links instead. The named alternative covers the most likely confusion with a single, concrete condition.

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