Skip to main content
Glama

AI Search (GEO), Crawler Access & llms.txt Readiness Audit

audit_ai_search_visibility
Read-onlyIdempotent

Inspect a URL for AI search visibility: check robots.txt rules for major AI crawlers, validate llms.txt indexes, and extract Schema.org JSON-LD entities to identify citation-readiness fixes.

Instructions

Inspect a live website URL for Generative Engine Optimization (GEO) and AI assistant citation readiness: verifies whether /robots.txt allows 8 major AI search crawlers (OAI-SearchBot, GPTBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot), validates /llms.txt and /llms-full.txt Markdown indexes, and extracts Schema.org application/ld+json entities. Use this tool for AI SEO and /llms.txt checks on a single URL; use full_launch_readiness_audit when running a complete pre-launch sweep.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic website URL or domain to inspect (e.g. 'https://cal.com' or 'linear.app').

Output Schema

NameRequiredDescriptionDefault
urlYesNormalized URL inspected.
gradeYesLetter grade from A to D.
scoreYes0-100 AI Search Visibility Score.
issuesYesActionable GEO visibility fixes.
llmsTxtYes/llms.txt and /llms-full.txt availability details.
checkedAtYesISO-8601 UTC timestamp.
aiCrawlersYesAllowed and blocked AI crawler summary.
upgradeLinksNoLinks for automated 500-page /llms.txt compilation.
structuredDataNoDetected Schema.org JSON-LD types and metadata tags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=true), so the bar is lower. The description does add real scope detail beyond that — which paths are fetched and which specific crawler tokens are checked — but it says nothing about runtime behavior such as timeouts, what happens on unreachable sites, or whether a fetch is rate-limited. That is a meaningful gap for a tool that performs outbound live requests.

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?

Two sentences, front-loaded with the verb and resource, then terminated with a routing rule. The enumeration of 8 crawler tokens is long but functions as a definition of scope rather than filler; still, it could have been compressed without losing routing value.

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?

An output schema exists, so return-value explanation is not required. For a one-parameter, read-only audit the description supplies the check list, the routing decision, and the scope constraint — everything an agent needs before calling.

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 the single parameter is fully documented with format examples ('https://cal.com' or 'linear.app'). The description reinforces the single-URL scope but adds no syntax or format information beyond what the schema already provides, so 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 (inspect) and resource (a live website URL) and enumerates the exact checks performed: robots.txt handling for 8 named AI crawlers, /llms.txt and /llms-full.txt validation, and JSON-LD entity extraction. It also names the sibling (full_launch_readiness_audit) it is not, so an agent can distinguish it without opening either 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 final sentence gives an explicit routing rule: this tool for AI SEO and /llms.txt checks on a single URL, full_launch_readiness_audit for a complete pre-launch sweep. Both the when and the alternative are stated, leaving nothing to inference.

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