Skip to main content
Glama

SEO technical audit

seo.audit

Audits Next.js codebases for SEO and AI-readiness (AEO), scoring crawlability, extractability, and citation readiness, and generates advise-only fix diffs without writing to the repository.

Instructions

Secondary alias of the audit engine. Prefer qualitykit.audit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectRoot": "<projectRoot>"
    },
    "name": "seo.audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlNo
projectRootYesAbsolute path to the website repository root
includeRenderedNoWhen true and siteUrl is set, fetch rendered HTML for key routes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and provides almost nothing: no indication of whether the audit mutates the repository, whether it makes network requests (the includeRendered parameter implies fetching rendered HTML), or what the result looks like. "Alias" implies behavioral parity with qualitykit.audit, but the agent cannot verify that from this text.

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?

Two short sentences with zero filler and the routing advice up front. The efficiency comes at the cost of substance, but there is no wasted wording to trim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Three parameters, no annotations, no output schema, and partial schema coverage leave the description doing far too little for a tool that takes a repository path and may fetch live HTML. It functions as a deprecation stub rather than a usable definition.

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

Parameters2/5

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

Schema description coverage is 67%, below the high-coverage threshold, so the description should compensate and adds nothing about projectRoot, siteUrl, or includeRendered. In particular the interaction between siteUrl and includeRendered (only fetches when siteUrl is set) is left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies this as an alias of "the audit engine", which combined with the title conveys a technical SEO audit, but the verb and scope of what the audit actually does are never stated. Its real value is signaling duplication with qualitykit.audit, not explaining the tool's function.

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?

"Prefer qualitykit.audit" is an explicit routing instruction naming the alternative, which is exactly what an agent needs to avoid this tool. It stops short of saying when this alias would still be legitimate to call (e.g. backward compatibility), so it is clear rather than exhaustive.

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