GoAI Moat AI Visibility Audit

Audit Ai Visibility

audit_ai_visibility

Deep-audit a brand's visibility in AI answers (ChatGPT, Perplexity, AI Overviews).

FREE TIER: 1 full deep audit per email — pass your email to unlock it. DEVELOPER/UNLIMITED: pass an api_key (or license_key) from a developer subscription at https://goaimoat.gumroad.com/l/njpksu to run audits programmatically with no email. Without email/api_key you get the audit framework and tier mapping only.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	No	Your email — unlocks 1 free full audit.
`score`	No	Optional known 0-30 checklist score. If provided, a tier + fix plan is included for free.
`api_key`	No	Developer API key — equivalent to license_key, for agent/API callers.
`category`	No	Product/service category (e.g. "phone case", "DTC fashion").
`brand_name`	Yes	The brand/company to audit.
`license_key`	No	Gumroad license key — unlocks unlimited full audits.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

addedInput schema / properties / api_key

Added value: +{
+  "default": "",
+  "description": "Developer API key — equivalent to license_key, for agent/API callers.",
+  "type": "string"
+}

First observedSep 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses tier gating, per-email limits, programmatic entitlement via keys, and the degraded output when unauthenticated. It stops short of describing runtime characteristics such as rate limits, latency, or external API calls, which would complete the picture for a long-running audit.

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-loaded with the core purpose, followed by tightly organized tier sections that each earn their place. Formatting is slightly shouty (ALL-CAPS tier labels) but no sentence is wasted.

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?

An output schema exists, so return values need not be explained, and the description covers auth paths, credentials, and tier behavior thoroughly. The only gap is that it never mentions the optional category or score parameters in prose, but the schema descriptions are complete for those.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it clarifies the relationship between api_key and license_key, that email unlocks exactly one free audit, and that omitting credentials changes the result to framework-only. That is more than the schema's per-field strings convey.

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+resource ('deep-audit a brand's visibility') and names the surfaces measured (ChatGPT, Perplexity, AI Overviews). This is clearly distinguishable from the sibling tools (checklist, category leaders, fix priority, usage, license check), so an agent can route to it without opening the schema.

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?

Explicitly lays out the tier conditions: email unlocks one free full audit, api_key/license_key enables unlimited programmatic runs, and without either you get only the framework and tier mapping. It gives clear when-to-use context but does not name alternatives or state when not to use it.

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

All GoAI Moat AI Visibility 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.