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

SEO audit (whole site)

site_seo_audit
Read-onlyIdempotent

Crawl a website and audit each page to aggregate average SEO scores, common issues, duplicate titles/descriptions, broken pages, and worst performers for site health reports and fix prioritization.

Instructions

Crawl a website (sitemap.xml or same-origin links, robots.txt respected) and run seo_audit on every page, then aggregate: average score, the most common issues with how many pages each affects, duplicate titles and meta descriptions, broken pages (4xx/5xx/unreachable) and the worst-scoring pages. Use it for site health reports and to prioritise fixes across many pages. Keep max_pages small (10-30) for a quick overview.

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

Input Schema

NameRequiredDescriptionDefault
urlYesStart URL. Only pages on the same origin (scheme + host + port) are crawled.
strategyNo"auto" uses sitemap.xml when available and falls back to following links; "sitemap" or "links" force one method.auto
max_depthNoLink depth from the start URL (only used by the "links" strategy).
max_pagesNoMaximum pages to fetch (hard cap 100).
path_prefixNoOnly crawl URLs whose path starts with this, e.g. "/blog/".

Output Schema

NameRequiredDescriptionDefault
crawlYes
pagesYes
worstPagesYes
brokenPagesYes
issueCountsYes
averageScoreYes
pagesAuditedYes
duplicateTitlesYes
duplicateDescriptionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: robots.txt compliance, same-origin restriction, sitemap-vs-links strategy, and the fact that unreachable/4xx/5xx pages are reported. It omits runtime/rate-limit expectations for what can be a slow multi-page crawl.

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 core action, then the aggregation output, then usage and a practical tip — a logical progression with little filler. Some of the aggregation listing is arguably redundant given an output schema exists, which keeps it from a 5.

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 five-parameter, open-world crawling tool with full annotations and an output schema, the description covers scope, safety, crawl method, and practical limits. An agent has everything needed to call it correctly without reading further.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds operational meaning by recommending small max_pages values for quick runs and tying crawl behavior to the sitemap/link strategy. It still doesn't clarify path_prefix or max_depth semantics beyond the schema.

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 specific verbs and resource: crawl a website then run seo_audit on every page and aggregate results. It also scopes the crawl mechanics (sitemap.xml or same-origin links, robots.txt respected), which clearly separates it from the single-page seo_audit and from crawl_site.

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?

Explicitly says 'Use it for site health reports and to prioritise fixes across many pages', giving a clear context for selection, and adds a practical sizing hint ('Keep max_pages small (10-30) for a quick overview'). It does not explicitly name a sibling as the alternative for single-page checks, so it stops short of full when/when-not routing.

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