Skip to main content
Glama
sparrow84001

SEO, AEO, GEO & Digital Marketing Audit + Safe Fix MCP Server

by sparrow84001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

seo_audit_sitemap_multipage

Crawls every page in a sitemap, checks robots.txt rules and security headers, then compiles a site-wide SEO scorecard and inventory report.

Instructions

Crawls and batch-audits all pages registered in a website sitemap.xml (or local discovered routes), cross-checks robots.txt allow/disallow rules, audits HTTP security headers (HSTS, CSP, X-Frame-Options), and compiles a site-wide scorecard and inventory report.

USAGE GUIDELINES:

  • Use when auditing an entire website with multiple pages rather than a single URL.

  • Do NOT use for single page analysis; use 'seo_generate_full_audit' instead for faster single-page feedback.

  • Do NOT use to generate new sitemaps; use 'seo_generate_sitemap_and_robots' instead.

BEHAVIORAL TRANSPARENCY:

  • Read-only batch crawl.

  • Issues HTTP GET requests respecting robots.txt directives and maxPages limits. Makes no disk modifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesWebsite base URL (e.g. "https://example.com") or local codebase folder path.
maxPagesNoMaximum number of sitemap URLs to crawl and audit (default: 25, recommended max: 50).
userAgentNoTarget crawler user-agent to evaluate robots.txt permissions against (default: "Googlebot").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • changedInput schema / properties / maxPages / description
      Previous value: -"Maximum number of sitemap URLs to crawl and audit (default: 25)."New value: +"Maximum number of sitemap URLs to crawl and audit (default: 25, recommended max: 50)."
    • changedInput schema / properties / target / description
      Previous value: -"Website URL (https://...) or local codebase folder path."New value: +"Website base URL (e.g. \"https://example.com\") or local codebase folder path."
    • changedInput schema / properties / userAgent / description
      Previous value: -"Target crawler user-agent to test robots.txt permissions against (default: Googlebot)."New value: +"Target crawler user-agent to evaluate robots.txt permissions against (default: \"Googlebot\")."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well. It discloses that the tool is read-only, issues HTTP GET requests, respects robots.txt directives and maxPages limits, and makes no disk modifications. This is strong behavioral transparency for a network-crawling tool.

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?

The definition is well structured and front-loaded: the opening sentence explains scope and outputs, the usage guidelines give clear routing, and the behavioral transparency section is terse yet complete. Every sentence adds distinct value.

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?

The description covers what the tool does, when to use it, and its safety profile, which is enough for selection and invocation. It mentions it compiles a scorecard and inventory report, but since there is no output schema, slightly more detail about the returned report format would make it fully complete.

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 baseline is 3. The description reinforces that maxPages limits the crawl and that robots.txt is checked, but it does not add substantive parameter meaning beyond the schema's own documentation.

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?

The description states a specific verb (crawls/batch-audits), a clear resource (sitemap.xml or local discovered routes), and distinct operations (robots.txt cross-check, security header audit, site-wide scorecard). It clearly separates this multi-page tool from single-page and sitemap-generation siblings.

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?

Usage guidelines are explicit: use for entire websites with multiple pages, do not use for single-page analysis (use seo_generate_full_audit), and do not use for sitemap generation (use seo_generate_sitemap_and_robots). This gives an agent direct routing cues with sibling names.

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

Deploy Server

Other Tools