Skip to main content
Glama

Plunder & Riffle Meme Engine

SEO audit of a website

seo_audit
Read-only

Full SEO + AI-search audit of ONE website from its url (the SEO Audit Factory engine: 50 measured checks — technical, content, AI readiness, local, performance — crawled the way AI/search crawlers receive the page, no JS execution). Free. Returns scores + grade, every finding with measured evidence and its fix, reportMarkdown (the complete end report, closing with the Muse prompts and the free-bot invite), musePrompts { fix, content, buildBot } — copy-paste prompts the human hands to their Muse — and invite (Muse invite code + the free-bot offer). Honest limits: no rankings, traffic or backlink claims; a site that blocks the crawl gets a limited report with the unmeasured categories named. Takes ~10–20s.

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
urlYesThe website to audit, http(s). A bare domain gets https:// added.
nameNoOptional business name (sharpens the report and prompts).
industryNoOptional trade/industry, e.g. "plumber".
locationNoOptional city/area the business serves, e.g. "Raleigh, NC".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 goes well beyond them by disclosing cost (free), latency (~10–20s), crawl semantics (no JS execution, crawled as AI/search crawlers see it), failure behavior for blocking sites, and explicit honesty limits (no rankings, traffic or backlink claims). That is exactly the behavioral context an agent needs before committing to the call.

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-loads the purpose and result shape before the caveats, and every clause carries information (checks, returns, limits, timing). It is dense and backtick-heavy in a single run-on paragraph, so scanning takes effort, but little is genuinely wasted.

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, and the description compensates by enumerating what comes back: scores plus grade, findings with measured evidence and fixes, reportMarkdown, musePrompts with its three keys, and invite. Combined with latency and failure-mode notes, nothing material is missing for a four-parameter, no-output-schema 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 the four parameters (url, name, industry, location) are already documented in the schema itself. The description only restates that the audit keys off `url` and adds no new meaning for name/industry/location. Baseline 3 applies where the schema does the heavy lifting.

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 ("Full SEO + AI-search audit of ONE website from its `url`") and pins down the engine and scope: 50 measured checks across technical, content, AI readiness, local and performance. The "ONE website" scoping and the AI-crawler framing separate it cleanly from the creation-oriented siblings in the catalog.

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?

Gives clear context for when this applies: a single URL, free of charge, ~10–20s, non-JS crawl. It also sets expectations for the edge case where a site blocks the crawl (limited report with unmeasured categories named). It stops short of naming explicit alternatives or when-not-to-use conditions, which is the only gap.

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.

Resources