Skip to main content
Glama

Audit SEO metadata

audit_seo_metadata
Read-onlyIdempotent

Use this for a focused SEO/accessibility-signal check of supplied HTML. It does not fetch a live webpage; use audit_public_webpage for a URL.

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": {
      "html": "<html>"
    },
    "name": "audit_seo_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesRaw HTML markup supplied by the user; this is not a webpage URL.

Output Schema

NameRequiredDescriptionDefault
errorNo
issuesYes
overviewYes
truncatedYes
total_issuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • 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"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / overview / properties / kind / enum
      Previous value: -[
      -  "html",
      -  "css",
      -  "seo",
      -  "schema",
      -  "links",
      -  "report"
      -]New value: +[
      +  "html",
      +  "css",
      +  "seo",
      +  "schema",
      +  "links",
      +  "report",
      +  "site"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / html / description
      Added value: +"Raw HTML markup supplied by the user; this is not a webpage URL."
  4. Changed3 schema fields changed
    • addedOutput schema / properties / error
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / overview
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "counts": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "key": {
      +            "type": "string"
      +          },
      +          "label": {
      +            "type": "string"
      +          },
      +          "tone": {
      +            "enum": [
      +              "error",
      +              "warning",
      +              "info",
      +              "success"
      +            ],
      +            "type": "string"
      +          },
      +          "value": {
      +            "maximum": 9007199254740991,
      +            "minimum": 0,
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "key",
      +          "label",
      +          "value",
      +          "tone"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "detail": {
      +      "type": "string"
      +    },
      +    "headline": {
      +      "type": "string"
      +    },
      +    "kind": {
      +      "enum": [
      +        "html",
      +        "css",
      +        "seo",
      +        "schema",
      +        "links",
      +        "report"
      +      ],
      +      "type": "string"
      +    },
      +    "next_action": {
      +      "type": "string"
      +    },
      +    "shown": {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "status": {
      +      "enum": [
      +        "passed",
      +        "needs_attention",
      +        "partial",
      +        "failed",
      +        "not_applicable"
      +      ],
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "total": {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "kind",
      +    "status",
      +    "title",
      +    "headline",
      +    "detail",
      +    "total",
      +    "shown",
      +    "truncated",
      +    "counts"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "issues",
      -  "total_issues",
      -  "truncated"
      -]New value: +[
      +  "issues",
      +  "total_issues",
      +  "truncated",
      +  "overview"
      +]
  5. Changed3 schema fields changed
    • addedOutput schema / properties / total_issues
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "issues"
      -]New value: +[
      +  "issues",
      +  "total_issues",
      +  "truncated"
      +]
  6. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds meaningful context by confirming it operates solely on supplied markup and performs no network fetch, reinforcing openWorldHint=false rather than contradicting it.

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 short sentences with the primary use front-loaded and the exclusion/alternative immediately after. Every clause carries information; nothing is redundant or padded.

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?

With one required parameter, full schema coverage, and an output schema that carries return values, the description covers everything needed to invoke it correctly. Its only shortfall is not clarifying the boundary against sibling validators that accept the same HTML input.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains that 'html' is raw markup and not a URL. The description restates that distinction at the tool level but adds no new syntax, size, or format semantics beyond the schema.

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

Purpose4/5

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

The description gives a specific verb ('check') and resource ('supplied HTML') scoped to SEO/accessibility signals, and explicitly names audit_public_webpage as the tool for URLs. It does not, however, distinguish itself from validate_html or validate_schema_markup, which appear to overlap with the same input.

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?

It states the intended use ('focused SEO/accessibility-signal check of supplied HTML') and an explicit when-not plus alternative ('It does not fetch a live webpage; use audit_public_webpage for a URL'). No guidance is given on when to prefer it over validate_html/validate_schema_markup for the same HTML input.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources