Skip to main content
Glama
Sign In
Web Validator by DigestSEO

Web Validator by DigestSEO

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Audit SEO metadata

seo.metadata
Read-onlyIdempotent

Audits supplied HTML offline for on-page SEO metadata, headings, viewport, image alt text, and Open Graph issues so you can identify and fix local markup problems quickly.

Instructions

Audits supplied HTML offline for on-page SEO metadata, headings, viewport, image alternatives, and Open Graph issues. Use for a quick on-page check; use html.local/html.url for W3C HTML validation, schema.markup for JSON-LD syntax, or report.validation for a combined local-file report.

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": {
      "htmlContent": "<htmlContent>"
    },
    "name": "seo.metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlContentYesRaw HTML markup to inspect locally.

Output Schema

NameRequiredDescriptionDefault
errorNo
countsYes
issuesYes
truncatedYes
totalIssuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.28
    • addedOutput schema / properties / counts
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "info": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "warning": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "error",
+    "warning",
+    "info"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / issues / items / properties / code
      Added value: +{
+  "description": "Stable machine-readable audit rule identifier.",
+  "type": "string"
+}
    • changedOutput schema / properties / issues / items / required
      Previous value: -[
-  "severity",
-  "category",
-  "message"
-]New value: +[
+  "code",
+  "severity",
+  "category",
+  "message"
+]
    • changedOutput schema / required
      Previous value: -[
-  "issues",
-  "totalIssues",
-  "truncated"
-]New value: +[
+  "issues",
+  "totalIssues",
+  "truncated",
+  "counts"
+]
  2. Addedv1.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world; the description's 'supplied HTML' and 'offline' wording reinforces that nothing is fetched, which is useful confirmation. It also scopes exactly which audit categories run, but says nothing about the result shape or how issues are counted/severity-ranked — acceptable given an output schema exists.

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?

Two sentences, zero filler. The capability statement is front-loaded and the disambiguation/routing clause follows, which is exactly the order an agent needs.

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?

With annotations covering the safety profile and an output schema covering return values, the remaining burden on the description is scope and sibling routing — both fully discharged. Nothing an agent needs in order to call this correctly 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?

Only one parameter and the schema already documents it at 100% coverage, so the baseline applies. The description still adds a meaningful disambiguation beyond the schema: the input is 'supplied HTML' inspected locally, making clear the parameter is raw markup rather than a URL or path.

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?

Names a specific verb (audits) and resource (supplied HTML) plus the exact check categories: SEO metadata, headings, viewport, image alternatives, Open Graph. The word 'offline' scopes it against the URL-fetching siblings, so an agent can distinguish it from html.url without opening a schema.

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 the selection rule ('use for a quick on-page check') and then routes three named alternatives to their specific conditions: html.local/html.url for W3C validation, schema.markup for JSON-LD, report.validation for a combined local-file report. Both when-to-use and when-to-look-elsewhere are covered.

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