Skip to main content
Glama

Quick on-page SEO audit with a 0-100 score

seo_audit
Read-only

Quick on-page SEO audit with a 0-100 score: title and meta description length, H1, canonical, lang, viewport, noindex, Open Graph, image alt text, structured data, HTTPS, robots.txt and sitemap, with a fix for each failed check. Takes 2-5 s. Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.005 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantially more: expected latency of 2-5 s, a hard free-tier throttle of 20 calls/day per user across free tools, and a metered paid tier at $0.005/call settled via x402 in USDC on Base. It also discloses that each failed check comes with a fix, which tells the agent what the response contains behaviorally.

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, front-loaded with the score and check list, then cost/limit facts. The long comma-separated check list is dense but each item earns its place by defining scope. Slightly list-heavy phrasing prevents a 5.

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 readOnly/openWorld annotations and no output schema, the description carries the burden well: it explains what the score means, what checks are run, that fixes are returned, how long it takes, and how billing works. The one gap is scope clarity — it does not say explicitly whether the audit is limited to the single supplied URL or fetches robots.txt/sitemap site-wide, which matters for an openWorld tool.

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 both url and payment are already well documented, including the two-step "omit first to get requirements" flow and the gasless USDC detail. The description's pricing sentence reinforces the payment parameter's economics but adds no syntax, format, or constraint that the schema lacks, so the baseline of 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 ("on-page SEO audit") and immediately enumerates the exact checks performed (title/meta length, H1, canonical, lang, viewport, noindex, Open Graph, alt text, structured data, HTTPS, robots.txt, sitemap). That enumeration is what separates it from single-concern siblings like meta, headings, images, robots, and https_check, which each cover only one of these checks.

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?

Usage is implied rather than stated: the agent can infer this is the aggregate audit to reach for when it wants a scored overview instead of individual checks, and the payment flow note ("Omit on the first call to get the price and requirements") is a genuinely useful invocation instruction. However, no sibling is named and there is no explicit when-not guidance (e.g. whether it audits one URL only, or whether to call granular tools for detail).

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.