Skip to main content
Glama

AEO Audit

by no.synligdigital

audit_domain_premium

Read-only

Premium AEO audit. Subscribe at https://buy.stripe.com/dRmbJ1cJh72E3TO57agjC00 ($9/mo unlimited) or pay $0.10 USDC per call via x402. Includes everything in audit_domain PLUS:

  • Actionable recommendations with priority ranking

  • Technical implementation guide (llms.txt, structured data, FAQ schema)

  • Competitive gap analysis with specific improvement steps

  • Estimated score improvement per recommendation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain to audit (e.g., 'example.com')
queriesYesSearch queries to test
providerNoAI engine (default: perplexity)
competitorsNoCompetitor domains

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description focuses on additional behavioral context: the tool requires payment via subscription or per-call USDC, and it references external services (Stripe, x402). This adds valuable context about costs and external dependencies.

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?

The description is concise and front-loaded with the core purpose, followed by pricing and feature list. The bullet points improve scannability, and there is no redundant information.

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?

Given the absence of an output schema, the description adequately informs the user about what to expect in the output (recommendations, guide, analysis, score improvement). It also references the base audit_domain tool to inherit its behavior, providing sufficient context for a premium variant.

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?

The schema covers all parameters with descriptions, and the description does not add parameter-specific syntax or format details. However, it does imply the 'competitors' parameter is used for competitive gap analysis, which is a subtle enhancement.

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?

The description clearly identifies this as a 'Premium AEO audit' and lists specific deliverables (recommendations, implementation guide, competitive gap analysis). It distinguishes from the sibling audit_domain by stating 'Includes everything in audit_domain PLUS', making the scope 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?

The description implies usage when the user needs premium features beyond the basic audit, explicitly listing the added value. It also provides pricing and payment options, but does not explicitly state when not to use this tool or alternatives like quick_check.

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

All AEO Audit toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

audit_domain and audit_domain_premium are nearly identical in purpose, with premium being a superset, and quick_check also performs a similar visibility check. This creates significant ambiguity about which tool to use for a given task, despite distinct feature lists.

Naming Consistency2/5

Tool names mix patterns: 'audit_domain', 'audit_domain_premium', 'quick_check', and 'suggest_queries' vary between verb_noun, suffixed verb_noun, adjective_noun, and verb_noun. The inconsistency makes predicting tool names or extensions harder.

Tool Count5/5

With only 4 tools, the count is appropriate for a focused audit service. Each tool corresponds to a distinct workflow step or tier, and the number is well within the typical 3-15 range.

Completeness4/5

The set covers the full audit lifecycle: query generation, quick checks, full audits, and premium audits with recommendations. Minor gaps like historical audit tracking or comparison between runs exist, but core domain needs are well served.

Resources