Skip to main content
Glama

mcp-seo

by com.onrender.mcp-seo-5dl7
OverviewDiscussionsAdmin

seo_audit_sitemap_multipage

Read-onlyIdempotent

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 changed
    • 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 observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide read-only, idempotent, and non-destructive hints. The description adds valuable behavioral context beyond annotations: it issues HTTP GET requests, respects robots.txt and maxPages limits, and makes no disk modifications. This goes beyond the annotation hints, earning a 4.

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?

The description is structured with clear sections (purpose, usage guidelines, behavioral transparency). While longer than minimal, each section contributes essential information. The purpose is front-loaded, and the structure aids readability. It is not overly verbose for the tool's complexity, earning a 4.

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 purpose, usage, behavior, and gives an idea of output (scorecard and inventory report). It lacks output format details, but that is not critical given it is a crawl/audit tool. With annotations covering safety and schema covering parameters, the description is adequately complete for an agent to use correctly.

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?

All three parameters are fully described in the input schema (100% coverage), so the baseline is 3. The description does not add parameter-specific details beyond what the schema provides; it only indirectly references maxPages in the behavioral section. No extra value is added, so a 3 is appropriate.

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 clearly states the tool's function: it crawls and batch-audits all pages from a sitemap, cross-checks robots.txt, audits HTTP security headers, and compiles a site-wide scorecard. It explicitly distinguishes itself from single-page tools by referencing seo_generate_full_audit, making the purpose unambiguous.

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 description contains a dedicated USAGE GUIDELINES section that explicitly states when to use this tool (multi-page audits) and when not to (single-page or sitemap generation). It names the specific alternative tools (seo_generate_full_audit and seo_generate_sitemap_and_robots), leaving no decision to inference.

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

All mcp-seo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources