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. Returns: pass (bool), findings[] with id/severity/detail.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Live, fetchable http(s) URL to audit.
`html`	No	Raw HTML source to audit instead of fetching a URL.
`language`	No	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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`pass`	Yes
`status`	No
`findings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 1, 2026

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."
```

Changed1 schema field changedSep 27, 2026

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"
+}

Changed8 schema fields changedAug 25, 2026

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"
+}

First observedAug 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely new behavior: pricing at $0.05 per call and the rule-by-rule finding model with severity ('what is missing or malformed'). That is real added context beyond the annotations.

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?

Front-loaded with the core purpose, then the checked elements, then severity and return shape; the '$0.05 per call' cost is surfaced early. Slightly fragment-heavy but every clause carries information.

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?

For a read-only audit tool with a full output schema and complete parameter descriptions, the definition covers scope, input modes, cost, and finding format. The only gap is routing guidance relative to the other audit_* tools, which is minor given the distinct on-page-SEO scope.

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 100%, so the schema already documents url, html, and language. The description's 'live URL or raw HTML' mirrors the schema's anyOf but adds no syntax, format, or mutual-exclusion detail beyond it, so baseline 3 applies.

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+resource ('SEO audit of a web page') and enumerates the exact rule domains checked: title tag, meta description, H1 structure, canonical, OpenGraph, JSON-LD, html lang. The phrase 'on-page SEO check' cleanly separates it from audit_performance, audit_security, and audit_wcag without needing to name them.

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?

It communicates accepted inputs ('any live URL or raw HTML') and implies usage context for a page-level SEO check, but gives no explicit when-to-use-vs-alternative guidance — e.g. when to reach for audit_bundle instead, or whether raw HTML is preferred over fetching. Usage is implied rather than directed.

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

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

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.