SEO Audit

Check AI instructions

check_ai_instructions

Read-onlyIdempotent

Checks the site's AI instructions files and page. Use this when the user asks whether a site publishes llms.txt, llms-full.txt or an AI instructions page, whether the home page links to them, and whether the file matches the site's own name, products and facts. Pass the domain. Returns pass, warn or fail for each part, with the evidence URL and a fix, plus the date the pages were read. A public post is cited as the reason the check exists. It does not promise an effect on AI Overviews and does not query AI engines. For a local business site, use local_ai_readiness; to draft the file, use generate_ai_instructions. Do not use it for private addresses or to collect contact details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	A public website, for example example.com or https://example.com. Only that site's public pages are read.

Output Schema

TableJSON Schema

Name	Required	Description
`asOf`	Yes	UTC date the pages were read, YYYY-MM-DD.
`files`	Yes
`notes`	Yes
`checks`	Yes
`domain`	Yes
`effect`	Yes
`notice`	Yes
`reason`	Yes
`source`	Yes
`refused`	No
`summary`	Yes
`compared`	Yes
`finalUrl`	No
`homeLinks`	Yes
`reachable`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses the result shape (pass/warn/fail per part with evidence URL and fix), the read-date provenance, and critically the scope limits — it does not promise an effect on AI Overviews and does not query AI engines. That negative scoping prevents a plausible agent misconception.

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-loads the purpose and is otherwise well organized: usage, alternatives, exclusions in order. It is dense and runs long, but nearly every clause carries a distinct constraint, so only mild trimming is warranted.

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 an output schema present, return values need not be enumerated in detail, and the description still summarizes the verdict format and evidence. Combined with full usage routing and explicit exclusions, there is nothing an agent needs to invoke this correctly that is missing.

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 description coverage is 100% and there is a single parameter, so the schema already documents the domain format and the public-pages-only constraint. 'Pass the domain' adds no syntax or format detail beyond it, so the baseline 3 applies.

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 ('Checks the site's AI instructions files and page') and immediately scopes it to llms.txt, llms-full.txt and an AI instructions page, plus a name/facts consistency check. An agent can distinguish it from generate_ai_instructions and local_ai_readiness without reading 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?

Provides explicit when-to-use conditions (user asks whether a site publishes these files, whether the home page links to them, whether contents match the site), names two sibling alternatives with their selecting conditions, and adds clear exclusions (no private addresses, no contact-detail collection). Nothing is left to inference.

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

All SEO Audit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.