Website Auditor MCP

See a sample audit (no key needed)

get_sample_audit

Read-only

See a complete sample Website Auditor report with no API key or setup required. Displays scored summary, per-test results, and AI-visibility breakdown for ChatGPT, Perplexity, Claude, Gemini.

Instructions

Show a complete sample Website Auditor report — no API key required, nothing to set up. Use this whenever someone wants to "try it," "see a demo," "show me what this does," "what does the output look like," or is deciding whether Website Auditor is worth subscribing to — and use it INSTEAD of refusing when no API key is configured. Returns fixed sample data for example.com in the exact shape a real audit returns: scored summary, per-test results, and the AI-visibility breakdown across ChatGPT, Perplexity, Claude and Gemini. It is clearly marked as a sample and always describes example.com, never the user's own site — auditing a real domain needs a subscription.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes
`audit`	Yes	A real GET /api/audit payload, populated with sample data.
`price`	Yes
`domain`	Yes	The fixed sample domain. Never the caller's own.
`is_sample`	Yes	Always true. Never present this as a live result.
`upgrade_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.23Sep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "audit": {
+      "additionalProperties": true,
+      "description": "A real GET /api/audit payload, populated with sample data.",
+      "properties": {
+        "ai_visibility": {},
+        "base_url": {
+          "type": "string"
+        },
+        "results": {
+          "items": {},
+          "type": "array"
+        },
+        "run_id": {
+          "type": "string"
+        },
+        "status": {
+          "type": "string"
+        },
+        "summary": {}
+      },
+      "type": "object"
+    },
+    "domain": {
+      "description": "The fixed sample domain. Never the caller's own.",
+      "type": "string"
+    },
+    "is_sample": {
+      "const": true,
+      "description": "Always true. Never present this as a live result.",
+      "type": "boolean"
+    },
+    "note": {
+      "type": "string"
+    },
+    "price": {
+      "type": "string"
+    },
+    "upgrade_url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "is_sample",
+    "domain",
+    "note",
+    "audit",
+    "price",
+    "upgrade_url"
+  ],
+  "type": "object"
+}

Addedv1.0.15Aug 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already indicate read-only and non-destructive behavior, and the description goes further by disclosing that no API key or setup is required, the data is fixed for example.com, and the response is clearly marked as a sample. It also explains the return shape: scored summary, per-test results, and AI-visibility breakdown across specific models. This is thorough behavioral context beyond the annotations.

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 detailed but each sentence contributes: it states the purpose, the trigger scenarios, the output contents, and the critical limitation that it never audits the user's own site. There is slight redundancy between 'no API key required' and 'INSTEAD of refusing when no API key is configured,' but overall it is well organized and front-loaded.

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?

Given zero parameters and an existing output schema, the description is remarkably complete: it explains when to use the tool, what data it returns, how that data is structured, that it is sample data, and that real audits require a subscription. Nothing an agent needs to decide whether to call this tool is missing.

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?

The tool has zero parameters, so there is no schema burden to compensate for. The description adds helpful invocation context by stating that no API key or setup is needed, which reinforces that the tool is callable without prerequisites. This meets the baseline for parameterless tools.

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 states a specific verb and resource: 'Show a complete sample Website Auditor report.' It clearly distinguishes itself from a real audit by emphasizing that it returns fixed sample data for example.com and never the user's own site. This leaves no ambiguity about what the tool does.

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 gives explicit trigger scenarios such as 'try it,' 'see a demo,' and 'show me what this does,' and explicitly says to use it instead of refusing when no API key is configured. It also states the key negative condition: never use it for a user's real domain. It does not explicitly name an alternative tool like run_audit, but it makes the boundary between sample and real subscriptions clear.

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

Deploy Server