Skip to main content
Glama

Validate SEO changes

seo.validate

Validate a Next.js project or proposed file contents for SEO and AI-readiness, checking crawlability, extractability, and citation readiness before applying changes.

Instructions

Specialized validation of project or proposed files. Prefer qualitykit.verify for finding-level verification.

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.validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlNo
projectRootYesAbsolute path to the website repository root
proposedFilesNoOptional proposed file contents to validate without writing

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 and no output schema, the description carries the full behavioral burden yet supplies almost nothing: no indication of whether validation writes files, what checks are run, how findings are returned, or how long it takes. The only behavioral hint ('without writing') is buried in the schema, not the description.

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, front-loaded sentences with no filler. However, the brevity edges into under-specification rather than disciplined conciseness for a validation tool.

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?

A validation tool with three parameters, no annotations, and no output schema needs more: what constitutes a valid result, what validation categories are checked, and whether the repo is modified. The description says none of this, leaving the agent to guess at outcomes.

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?

At 67% schema description coverage, the schema already documents projectRoot and proposedFiles, and the description only loosely maps 'project or proposed files' to those two. The undocumented siteUrl parameter gets no clarification in the description, so no real meaning is added beyond 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?

Names a verb (validate) and vague objects ('project or proposed files'), but never says what is being validated for -- presumably SEO properties inherited from the seo namespace. It does differentiate from qualitykit.verify, which helps, but the core purpose remains underspecified.

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

Usage Guidelines3/5

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

Provides one explicit exclusion: prefer qualitykit.verify for finding-level verification. That implies this tool covers project-level or pre-write file validation, but the positive when-to-use condition and any prerequisites (auth, site profile setup) are left implicit.

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