Skip to main content
Glama

audit_seo

Read-onlyIdempotent

Full SEO technical audit of a single web page URL. Fetches the page server-side plus the origin's robots.txt and sitemap, and runs 13 weighted checks: robots.txt present, robots not blocking the page, no noindex directive, sitemap present and valid, title tag length, meta description length, canonical tag, viewport (mobile), H1 structure, Open Graph completeness, JSON-LD structured data, image alt coverage, and a fetch-performance signal. These are the technical failures that make a page invisible in search — a robots-blocked or noindexed page cannot rank at all, and a missing sitemap, title, or canonical quietly caps the rest. Returns machine-readable JSON: 0-100 score, A-F grade, a search-visibility risk level (Low/Moderate/Elevated/High) with the blocking checks named as triggers, per-check pass/partial/fail/unknown with evidence, a page block (status, bytes, fetch time, title, sitemap URL), and the top 3 prioritized fixes. HONEST LIMITS: this is a single-page snapshot — it does not crawl the site, and it uses no keyword, ranking, backlink, or Search Console data; no audit can guarantee ranking. Cost: $1.00 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this after a redesign or template change, before a launch, or to triage a sudden traffic drop.

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": "audit_seo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWeb page URL to audit, e.g. https://example.com/pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, but the description adds substantial context beyond them: fetching robots.txt and sitemap, running 13 weighted checks, returning a 0-100 score with grade and risk level, and paying $1.00 USDC via x402 with no API key. It also discloses limitations around crawling, keyword data, backlinks, and Search Console.

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?

Although long, the description is front-loaded with the purpose, then moves through checks, return values, limits, cost, and usage. Every block earns its place by helping an agent decide whether and how to call a paid audit tool.

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?

There is no output schema, so the description carries the return-value burden and does so thoroughly: score, grade, risk level with triggers, per-check evidence, page metadata, and top fixes. It also covers payment, authentication, and scope limits, making the definition complete for this complexity.

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 URL parameter with 100% schema description coverage, and the schema already supplies the example format. The description reinforces that this is a single web page URL but does not add constraints, formats, or edge-case guidance beyond the schema, so the baseline 3 is appropriate.

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 states a specific verb and resource: a full technical SEO audit of a single web page URL, with 13 named checks. The word 'Full' hints at a lighter sibling, but it never names audit_seo_lite or explicitly contrasts the checks, so sibling differentiation is only implicit.

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 gives clear use cases: after a redesign or template change, before launch, or to triage a traffic drop. The 'HONEST LIMITS' section also clarifies that it is a single-page snapshot rather than a site crawl, though it does not explicitly say when to choose audit_seo_lite instead.

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.