Skip to main content
Glama
sparrow84001

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

by sparrow84001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

seo_generate_sitemap_and_robots

Generate standard-compliant sitemap.xml and robots.txt with directives for Googlebot, Bingbot, and AI search engines to fix missing or outdated configuration files.

Instructions

Generates production-ready, standard-compliant sitemap.xml and robots.txt files with crawler directives for Googlebot, Bingbot, and AI search engines (GPTBot, ClaudeBot, PerplexityBot).

USAGE GUIDELINES:

  • Use when a website is missing sitemap.xml or robots.txt, or needs clean, updated configuration files.

  • Do NOT use to audit existing files; use 'seo_audit_robots_and_sitemap' instead.

  • Do NOT use to crawl pages; use 'seo_audit_sitemap_multipage' instead.

BEHAVIORAL TRANSPARENCY:

  • Pure generation tool. Returns formatted XML and robots.txt file contents as text output. Does not write to disk directly unless copied by user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsNoList of relative or absolute URLs to register in sitemap.xml (e.g. ["/", "/about", "/pricing"]).
targetUrlYesBase website domain URL (e.g. "https://example.com").
disallowedPathsNoURL path prefixes to disallow in robots.txt (e.g. ["/admin/", "/api/private/"]).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • changedInput schema / properties / disallowedPaths / description
      Previous value: -"Paths to disallow in robots.txt (e.g. [\"/admin/\", \"/api/private/\"])."New value: +"URL path prefixes to disallow in robots.txt (e.g. [\"/admin/\", \"/api/private/\"])."
    • changedInput schema / properties / targetUrl / description
      Previous value: -"Base website URL (e.g., https://example.com)."New value: +"Base website domain URL (e.g. \"https://example.com\")."
    • changedInput schema / properties / urls / description
      Previous value: -"Array of relative or absolute URLs to register in sitemap.xml."New value: +"List of relative or absolute URLs to register in sitemap.xml (e.g. [\"/\", \"/about\", \"/pricing\"])."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Without annotations, the description carries the full burden, and it does so well by stating this is a pure generation tool, returns file contents as text, and does not write to disk directly. This is a meaningful disclosure of side effects and output format, though it could also mention failure behavior or permissions if relevant.

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 description is well-organized into clear sections: a concise main summary, usage guidelines with routing exclusions, and a short behavioral transparency note. Every sentence earns its place and the critical information is front-loaded.

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?

The tool is simple (3 params, all schema-documented) and the description explicitly states the output format, the side-effect behavior, and when to use alternatives. Even without an output schema, an agent has enough information to invoke it correctly and understand the result.

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 input schema fully explains targetUrl, urls, and disallowedPaths. The description itself does not add parameter-level detail beyond what the schema already provides, so a baseline score of 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 opens with a specific verb ('Generates') and identifies the exact resources produced ('sitemap.xml and robots.txt files') along with the crawler directives they include. This clearly distinguishes it from the sibling audit tools like seo_audit_robots_and_sitemap.

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 explicitly state when to use the tool (missing or outdated files, clean configuration needed) and when not to, naming the exact sibling alternatives for audits and crawling. This gives an agent direct routing instructions with no ambiguity.

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