Skip to main content
Glama
SEO Audit MCP

SEO Audit MCP

by Nexariza-AI

Check robots.txt, sitemap and llms.txt

check_site_files

Audit a site’s robots.txt, sitemaps, and /llms.txt to verify crawler and AI assistant access, count sitemap URLs, and sample their status.

Instructions

For a site origin: reads robots.txt (and which AI crawlers it blocks), finds and counts sitemap URLs, samples a few for status, and checks for /llms.txt used by AI assistants.

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": {
      "site": "<site>"
    },
    "name": "check_site_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site origin, e.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden: it discloses that it reads robots.txt, reports AI crawler blocks, and only 'samples a few' sitemap URLs for status, which usefully implies partial and approximate results. It does not state that it is read-only, mention rate limits/timeouts, or describe the response shape.

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?

One front-loaded sentence with the scope constraint first and the three checks in sequence; dense but every clause carries content.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-part probe with no annotations and no output schema, the description is adequate on what is inspected but silent on result structure, sampling size, and network limits an agent would need to interpret results.

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% for the single `site` parameter, so the baseline is 3. The description adds that it expects a site origin rather than a full URL path, which slightly reinforces the schema's format hint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb set and resources: reads robots.txt, finds/counts sitemap URLs, checks /llms.txt. An agent can tell this is a crawl-readiness/AI-visibility probe, distinct from check_links and audit_page, though no sibling is named.

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 only implied by 'For a site origin' and the enumeration of checks; there is no explicit when-to-use or when-not-to-use guidance versus check_links or audit_page.

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

Deploy Server

Other Tools