Skip to main content
Glama

HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News

SEO and metadata audit

audit_seo
Read-onlyIdempotent

SEO audit of a web page (on-page SEO check) for any live URL or raw HTML: title tag, meta description, H1 heading structure, canonical link, OpenGraph and social tags, JSON-LD structured data, html lang attribute. Rule-by-rule findings with severity and what is missing or malformed. $0.05 per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_seo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
htmlNo
languageNo

Output Schema

NameRequiredDescriptionDefault
passYes
statusNo
findingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / html / description
      Removed value: -"Raw HTML source to audit instead of fetching a URL."
    • removedInput schema / properties / language / description
      Removed value: -"Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable text of the findings is returned in this language; rule ids, severities, URLs and numbers are untouched. Default: English."
    • removedInput schema / properties / language / examples
      Removed value: -[
      -  "ja"
      -]
    • removedInput schema / properties / url / description
      Removed value: -"Live, fetchable http(s) URL to audit."
    • removedInput schema / properties / url / examples
      Removed value: -[
      -  "https://example.com"
      -]
    • removedInput schema / title
      Removed value: -"Live URL or raw HTML to audit"
  2. Changed2 schema fields changed
    • removedInput schema / anyOf
      Removed value: -[
      -  {
      -    "required": [
      -      "url"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "html"
      -    ]
      -  }
      -]
    • addedInput schema / minProperties
      Added value: +1
  3. Changed6 schema fields changed
    • removedOutput schema / properties / findings / description
      Removed value: -"One entry per rule that did not pass. Empty when the check is clean."
    • removedOutput schema / properties / findings / items / properties
      Removed value: -{
      -  "detail": {
      -    "description": "What failed and where.",
      -    "type": "string"
      -  },
      -  "id": {
      -    "description": "Stable rule identifier.",
      -    "type": "string"
      -  },
      -  "severity": {
      -    "description": "Rule severity.",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / findings / items / required
      Removed value: -[
      -  "id"
      -]
    • removedOutput schema / properties / findings / items / type
      Removed value: -"object"
    • removedOutput schema / properties / pass / description
      Removed value: -"Whether every rule in this dimension passed."
    • removedOutput schema / properties / status / description
      Removed value: -"Present only on a completed audit."
  4. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable text of the findings is returned in this language; rule ids, severities, URLs and numbers are untouched. Default: English.",
      +  "examples": [
      +    "ja"
      +  ],
      +  "maxLength": 35,
      +  "pattern": "^[A-Za-z]{2,3}(-[A-Za-z0-9]{2,8})*$",
      +  "type": "string"
      +}
  5. Changed8 schema fields changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "url"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "html"
      +    ]
      +  }
      +]
    • changedInput schema / properties / html / description
      Previous value: -"Raw HTML to audit instead of a URL"New value: +"Raw HTML source to audit instead of fetching a URL."
    • changedInput schema / properties / url / description
      Previous value: -"Live URL to audit"New value: +"Live, fetchable http(s) URL to audit."
    • addedInput schema / properties / url / examples
      Added value: +[
      +  "https://example.com"
      +]
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / title
      Added value: +"Live URL or raw HTML to audit"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "properties": {
      +    "findings": {
      +      "description": "One entry per rule that did not pass. Empty when the check is clean.",
      +      "items": {
      +        "properties": {
      +          "detail": {
      +            "description": "What failed and where.",
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "Stable rule identifier.",
      +            "type": "string"
      +          },
      +          "severity": {
      +            "description": "Rule severity.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "pass": {
      +      "description": "Whether every rule in this dimension passed.",
      +      "type": "boolean"
      +    },
      +    "status": {
      +      "const": "ok",
      +      "description": "Present only on a completed audit.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "pass"
      +  ],
      +  "type": "object"
      +}
  6. First observed

TDQS

A3.9/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 open-world, so safety is covered. The description adds genuinely useful context beyond them: a per-call price of $0.05 and the shape of results ('rule-by-rule findings with severity and what is missing or malformed'). It does not discuss auth, rate limits or failure behavior on unreachable URLs, which keeps it below a 5.

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 sentences plus a price line, front-loaded with the scope and the enumerated checks, with no filler. The check list is long but each item earns its place by telling the agent what the report covers; only the trailing per-call price could be considered separable metadata.

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?

An output schema exists, so the description need not explain return values, and it still previews the rule-by-rule severity structure. Annotations cover the safety profile and the $0.05 cost is disclosed. The remaining incompleteness is the unexplained `language` parameter and url-vs-html precedence, which are moderate but not disqualifying gaps.

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?

Schema description coverage is 0%, so the description must carry the load; it partially does by signalling that either a live URL or raw HTML is accepted, matching the minProperties:1 constraint in spirit. It says nothing about the third parameter (language), nor what happens if both url and html are supplied (precedence), leaving real ambiguity around a core input decision.

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?

States a specific verb and resource ('SEO audit of a web page', 'on-page SEO check') and then enumerates exactly what is inspected: title, meta description, H1 structure, canonical, OpenGraph, JSON-LD, html lang. The 'on-page SEO' framing cleanly separates it from audit_wcag, audit_performance and audit_security, so an agent can pick it without opening the schema.

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?

'for any live URL or raw HTML' implies the two accepted input modes, but there is no explicit when-to-use versus when-not, no mention of audit_bundle for combined audits, and no guidance on which input mode to prefer. Usage is inferable rather than stated.

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.