Johto Data

Johto Data SEO Audit

seo_audit

Read-only

POST one page URL on a site you own or are authorized to audit. Returns on-page SEO as JSON: title, meta description, canonical, noindex, robots.txt and sitemap status, headings, images missing alt, links, schema.org types, hreflang, Open Graph, coded issues and a 0-100 score. Costs $0.005 USDC per call via x402. Without payment, the call returns the x402 payment requirements; retry with an X-PAYMENT or PAYMENT-SIGNATURE header, or params._meta["x402/payment"].

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": {
      "url": "<url>",
      "authorized": "<authorized>"
    },
    "name": "seo_audit"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Public http(s) page URL to audit
`authorized`	Yes	Must be true: you own this site or are authorized to audit it
`checkSitemap`	No	Read the sitemap to report whether the page is listed

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the supplied annotations (readOnlyHint=true, openWorldHint=false), the description discloses the per-call cost ($0.005 USDC via x402) and the exact two-step payment failure/retry protocol, which is the single most important behavior for an agent calling this tool. It also implies the authorization posture that makes the operation non-destructive and scoped.

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?

Three sentences ordered as purpose, return payload, and payment mechanics — the most decision-relevant facts come first. The long returns enumeration earns its space because there is no output schema to carry it.

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 no output schema, the description fully specifies the return shape and the 0-100 score, and it covers the cost/authorization model that governs whether the call succeeds. Nothing material for correct invocation is missing.

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`, `authorized`, and `checkSitemap`. The description reinforces the authorization requirement in prose and mentions sitemap status among outputs, but adds no syntax, format, or edge-case detail (e.g., redirect handling, non-HTML URLs) 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 uses a specific verb and resource ("POST one page URL" for an on-page SEO audit) and enumerates the returned artifacts, so an agent knows this is a single-page technical/on-page audit rather than a crawl or content extraction. It stops short of naming related siblings such as page_structured_extract, url_to_markdown, or sitemap_to_markdown, which would have made overlap unambiguous.

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 a clear precondition for use — the site must be owned or authorized, mirrored by the required `authorized` boolean — and explains the payment workflow (unpaid call returns x402 requirements; retry with a payment header or _meta field). It gives no explicit when-not or alternative-tool guidance against the many URL/extraction siblings.

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

All Johto Data 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.

Resources

Need Help?