Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

Sitemap validator

ayrank_sitemap_validate
Read-only

Validate XML sitemaps against sitemaps.org and Google rules, discover sitemap paths via robots.txt or /sitemap.xml, inspect child sitemaps, and HEAD-check sample URLs to catch indexing issues.

Instructions

Use to validate an XML sitemap (or find it from a site root via robots.txt, else /sitemap.xml) against the sitemaps.org protocol and Google's rules, including up to 10 child sitemaps of an index, then spot-check up to 20 listed URLs with HEAD. Not for checking every URL in a large sitemap, and not for hreflang in sitemaps.

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_sitemap_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA sitemap URL like https://example.com/sitemap.xml, or a site root like https://example.com.

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 already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely useful behavioral facts beyond that: the discovery fallback chain (robots.txt, else /sitemap.xml), hard caps of 10 child sitemaps and 20 HEAD requests. It does not say what the report contains or how truncation/partial coverage is surfaced, which is the main remaining gap.

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?

Front-loaded with 'Use to validate', followed by scope, limits, and exclusions — no filler sentences and every clause carries information. The parenthetical discovery aside slightly interrupts the flow, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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, open-world validator with no output schema, the description covers input forms, standards applied, request caps, and exclusions — enough to call it correctly. It stops short of indicating result shape or how incomplete coverage is reported, which a caller might want.

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 100% and the single parameter is fully described there, so baseline would be 3. The description nonetheless adds meaning by clarifying the two accepted input forms and, importantly, that a site-root input triggers discovery rather than failing — behavior the schema does not state.

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 ('validate an XML sitemap') plus the standards applied (sitemaps.org protocol, Google's rules) and the exact scope (up to 10 child sitemaps of an index, up to 20 HEAD spot-checks). The dual input mode — sitemap URL or site root with robots.txt/sitemap.xml discovery — is spelled out, so an agent can distinguish it from every other audit sibling 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?

Explicitly bounds usage on both sides: it validates the sitemap and spot-checks a sample of URLs, and it names two things it is not for — bulk-checking every URL in a large sitemap and hreflang-in-sitemaps analysis. That negative guidance steers an agent toward the appropriate alternative tool rather than over-using this one.

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