Skip to main content
Glama
web-insights-mcp
by nqcthedev

SEO audit (single page)

seo_audit
Read-onlyIdempotent

Run an on-page SEO audit for a single URL, returning a 0–100 score and a prioritized list of issues with severity levels and concrete fixes.

Instructions

Run an on-page SEO audit of one URL. Checks HTTP status/HTTPS/redirects, title and meta description length, H1 count and heading order, canonical, meta robots/X-Robots-Tag, viewport, lang, charset, Open Graph and Twitter tags, image alt text, JSON-LD presence and validity, internal/external links and anchor text, and thin content. Returns a 0-100 score and a prioritised issue list where every issue has a severity (error/warning/info) and a concrete fix. Use site_seo_audit for a whole site.

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
urlYesAbsolute http(s) URL. A bare domain like example.com is treated as https://example.com.

Output Schema

NameRequiredDescriptionDefault
urlYes
factsYes
scoreYes0-100; each error costs 15 points, each warning 5, each info 1.
issuesYes
passedYes
statusYes
summaryYes
finalUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety and network profile is covered. The description adds that results are a 0-100 score plus a prioritised issue list with severity levels and concrete fixes, but since an output schema exists this is largely restating structured data; no rate limits, auth needs, or fetch behavior beyond openWorld are mentioned.

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?

Purpose is front-loaded and the alternative is placed in a clear final sentence. The middle sentence is a long checklist of checks, which is information-dense and useful for setting expectations, though it borders on enumeration for its own sake.

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?

For a single-parameter, read-only audit tool with rich annotations and an output schema, the description covers what is examined, what is returned at a high level, and which sibling to use instead. Nothing essential to calling it correctly 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?

There is only one parameter and schema coverage is 100%, with the schema itself already explaining the absolute-URL requirement and the bare-domain normalization rule. The description adds no parameter-level meaning beyond the schema, 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 and resource ('Run an on-page SEO audit of one URL') and immediately scopes it to a single page, making it distinguishable from site-level work. The detailed checklist of what is checked reinforces the scope rather than obscuring it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The final sentence names the alternative ('Use site_seo_audit for a whole site') together with the exact condition that selects it, which is the key routing decision for this tool family. An agent can choose between the single-page and site-level tools without opening either schema.

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