Skip to main content
Glama
Sign In

SEO·AEO·GEO

by app.seoaeogeo
OverviewDiscussionsAdmin

Audit a page for Google and AI search

audit_url
Read-only

Audit one public web page for visibility in Google, AI Overviews, ChatGPT, Claude and Perplexity. Fetches the page as the AI search crawlers (OAI-SearchBot, Claude-SearchBot, PerplexityBot) to catch robots.txt, CDN and firewall blocks, checks how much content exists without JavaScript, and scores extractability and trust signals. Returns the score, every check's result and a fix pack: the fixes in priority order with where each lives in a codebase and a command to verify it. Takes 10–30 seconds.

Input Schema

NameRequiredDescriptionDefault
urlYesThe page to audit, e.g. https://example.com/pricing
questionNoOptional: the question this page should win in AI answers, e.g. "best CRM for small agencies". Adds query-level fit (heading match, answer-first for the question, names, price and date present); changes no score.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / question
      Added value: +{
+  "description": "Optional: the question this page should win in AI answers, e.g. \"best CRM for small agencies\". Adds query-level fit (heading match, answer-first for the question, names, price and date present); changes no score.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes much further, disclosing the fetch identity (OAI-SearchBot, Claude-SearchBot, PerplexityBot), what failure modes are surfaced (robots.txt, CDN and firewall blocks), that no-JS content volume is measured, and the 10–30 second runtime. That is exactly the kind of behavior an agent cannot get from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the action and targets, then method, then return shape, then runtime. Every sentence carries distinct information with no repetition of the schema or title.

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?

There is no output schema, and the description compensates by enumerating the return payload: the score, every check's result, and a priority-ordered fix pack with codebase locations and verification commands. For a two-parameter read-only tool with annotations, nothing material is left unspecified.

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%, so both `url` and `question` are already documented, including the note that `question` adds fit analysis without changing the score. The prose only reinforces the single-page scope and adds no new parameter semantics, so the 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?

States a specific verb and resource ('Audit one public web page') plus the exact scope of what is measured (Google, AI Overviews, ChatGPT, Claude, Perplexity). It never names the sibling get_report, so the agent must infer the split between running an audit and retrieving a report; otherwise the purpose is unambiguous.

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?

'Audit one public web page' and 'Takes 10–30 seconds' give clear selection context, including a latency expectation an agent can use to decide whether to call it inline. No explicit when-not-to-use or named alternative (get_report) is offered, so it stops short of full routing guidance.

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

All SEO·AEO·GEO toolsInspect
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.

Resources