Skip to main content
Glama
sparrow84001

SEO, AEO, GEO & Digital Marketing Audit + Safe Fix MCP Server

seo_generate_full_audit

Run an 8-dimension audit on a single URL. Get 0-100 scores, letter grades, prioritized action matrix, and a Markdown report.

Instructions

Executes the comprehensive 8-dimension audit suite across Technical, On-Page, AEO, GEO, Local, Content, CRO, and Performance. Calculates 0-100 scores, letter grades (A+ to F), P0-P3 prioritized action matrix, and formatted Markdown report.

USAGE GUIDELINES:

  • Use as the primary single-page audit tool when a complete health check and executive scorecard is needed.

  • Do NOT use for entire multi-page domain crawls; use 'seo_audit_sitemap_multipage' instead.

  • Do NOT use if you only need a single specific dimension; use the dedicated 'seo_audit_*' tools instead for faster response.

BEHAVIORAL TRANSPARENCY:

  • Safe, read-only comprehensive synthesis. Generates Markdown and JSON reports without modifying files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget live URL (e.g. "https://example.com") or local file path to audit.
projectPathNoOptional project root path for framework and routing context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / projectPath / description
      Previous value: -"Optional project root directory."New value: +"Optional project root path for framework and routing context."
    • changedInput schema / properties / target / description
      Previous value: -"Target file path or live URL."New value: +"Target live URL (e.g. \"https://example.com\") or local file path to audit."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden. It explicitly states 'Safe, read-only comprehensive synthesis' and 'Generates Markdown and JSON reports without modifying files', fully disclosing side effects and safety profile.

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?

The description is compact and well-structured: purpose, usage, and behavioral transparency each in a short sentence. No redundancy or filler.

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?

The description lists the audit dimensions and outputs (scores, grades, action matrix, Markdown/JSON reports), giving a solid functional overview. However, without an output schema, it does not specify the structure of the generated reports or the exact composition of the action matrix, which would be valuable for a comprehensive audit tool.

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 coverage is 100% with clear descriptions for both parameters. The description text adds no additional semantic detail beyond the schema, so the baseline of 3 is appropriate.

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?

Clearly states the tool executes a comprehensive 8-dimension audit across specified categories (Technical, On-Page, AEO, GEO, Content, CRO, Performance) and produces scores, grades, and an action matrix. This verb+resource combination differentiates it from single-dimension siblings.

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

Usage Guidelines5/5

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

Explicitly states when to use (primary single-page audit tool for complete health check) and when not to use (multi-page domain crawls → sitemap_multipage; single dimension → dedicated seo_audit_* tools). Leaves no ambiguity for selection.

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