Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

Internal link checker

ayrank_internal_links
Read-only

Lists internal links on a single page with anchor text, rel, placement, and flags for nofollow, self-links, empty or generic anchors, and Google-uncrawlable links, grouped by target for quick on-page link auditing.

Instructions

Use to list the internal links on ONE page with anchor text, rel and position (main, nav, footer), grouped by target, with flags for empty or generic anchors, nofollow, self-links and links Google cannot crawl. It does not crawl the site and does not fetch the links (use ayrank_broken_links for status codes). 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_internal_links"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description adds real value beyond that: the returned fields and flag categories, the no-crawl/no-fetch boundary, the no-key access model, and the limitation that JavaScript is not executed. It stops short of describing pagination or result limits, which keeps it from a 5.

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?

Three sentences, front-loaded with purpose, then output shape, then the sibling redirect, then the JS caveat. No redundant restatement of the tool name or title, and every clause carries operational 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?

For a one-parameter read-only tool with no output schema, the description compensates by enumerating the returned fields and flags and by stating the two major behavioral limits (no crawling/fetching, no JS execution). An agent has everything needed to call it correctly and interpret the result.

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?

With a single parameter at 100% schema coverage, the schema already carries the format and example URL. The description reinforces the 'ONE page' constraint, which clarifies that the URL is a single page rather than a site root, but adds no syntax or format 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 (list internal links) and narrows scope to exactly ONE page, then enumerates what is returned: anchor text, rel, position (main/nav/footer), grouping by target, and flags. It also distinguishes itself from ayrank_broken_links, so an agent can separate the two without opening a 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?

The opening 'Use to' plus explicit exclusions ('does not crawl the site and does not fetch the links') tell the agent both when this tool applies and when to route elsewhere, naming ayrank_broken_links as the alternative for status codes. The JS caveat further bounds when results are trustworthy.

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