Skip to main content
Glama
sparrow84001

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

by sparrow84001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

seo_audit_content

Assess content depth, search intent, word count thresholds, thin content risks, reading ease, and E-E-A-T signals. Identify quality gaps to improve editorial alignment.

Instructions

Evaluates content depth, search intent classification (Informational, Commercial, Transactional, Navigational), word count thresholds, thin content risks, reading ease, and Google E-E-A-T trust signals.

USAGE GUIDELINES:

  • Use to analyze article or landing page editorial quality, substance, and intent alignment.

  • Do NOT use for code-level schema validation; use 'seo_audit_schema' instead.

  • Do NOT use to generate marketing campaigns; use 'seo_generate_marketing_strategy' instead.

BEHAVIORAL TRANSPARENCY:

  • Safe, read-only content analysis. No file modifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget live URL (e.g. "https://example.com/blog/guide") or local file path to audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / target / description
      Previous value: -"Target file path or live URL."New value: +"Target live URL (e.g. \"https://example.com/blog/guide\") or local file path to audit."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The description explicitly states 'Safe, read-only content analysis. No file modifications.' Even though no annotations are provided, the description discloses the behavioral traits of safety and read-only nature.

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 concise, listing key evaluation criteria in a single sentence, followed by clear usage guidance and safety note. It is well-structured and front-loaded with the main purpose.

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 the tool's straightforward nature and lack of output schema, the description is sufficiently complete. It covers what the tool does, when to use it, and its safety profile. No additional context seems necessary.

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 input schema fully describes the 'target' parameter (URL or file path). The tool description does not add additional parameter-specific information, so it does not exceed the baseline for high schema coverage.

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 states the tool evaluates content depth, search intent classification, word count, thin content, reading ease, and E-E-A-T signals. It is specific about the function and distinguishes it from generic audits.

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?

The description explicitly states when to use (analyze article/landing page editorial quality) and when not to use, with alternatives for schema validation and marketing strategy. This provides clear guidance for tool selection.

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

Deploy Server

Other Tools