Skip to main content
Glama

AI Visibility Audit

Audit a site's AI-search readiness

audit_ai_readiness
Read-onlyIdempotent

Run a free live audit of a website's readiness to be found and quoted by answer engines (ChatGPT, Claude, Gemini, Perplexity, Google AI Overviews) and classic search. Fetches the home page and a few internal pages, robots.txt, sitemap.xml and llms.txt, then returns an AI-readiness score (0-100), an SEO hygiene score and pass/warn/fail checks with their meaning. Use it when the user asks whether their site is visible in AI answers or what to fix first.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe website to check, e.g. https://example.com or example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context: that it is free, that it performs live fetches of the home page, a few internal pages, robots.txt, sitemap.xml and llms.txt, and what the response contains. It stops short of stating latency, rate limits, or behavior when a URL is unreachable.

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 action and scope, then the concrete fetch/return details, then the usage trigger. The parenthetical list of answer engines is a mild expansion but it earns its place by widening the concept of 'AI search'; no filler sentences.

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?

With no output schema, the description carries the return-value burden and does so by naming the 0-100 AI-readiness score, SEO hygiene score, and pass/warn/fail checks with their meaning. Remaining gaps are minor for a one-parameter read-only tool: undefined latency/'a few internal pages' scope and no stated failure behavior for unreachable sites.

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?

There is a single parameter with 100% schema coverage, and the schema already supplies the example format with or without scheme. The description adds no further meaning about the url parameter (e.g., whether subdomains/paths are accepted or what happens on invalid input), so baseline 3 applies.

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?

The description gives a specific verb+resource ('Run a free live audit of a website's readiness to be found and quoted by answer engines') and enumerates what is fetched and returned. It implicitly distinguishes itself from narrower siblings like check_ai_crawler_access and check_schema_readiness by covering full readiness rather than a single check, but it never names or contrasts them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear when-to-use trigger: 'Use it when the user asks whether their site is visible in AI answers or what to fix first.' No when-not-to-use or explicit alternative routing is given, so an agent facing a narrow request (e.g., only fully crawler access) gets no guidance about the cheaper sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources