Skip to main content
Glama
Crawl Readiness MCP Server

Crawl Readiness MCP Server

Generate robots.txt

generate_robots_txt

Generates an AI-crawler-aware robots.txt for a website by merging existing rules with a selected allow, search-only, or block policy, returning a ready-to-save file.

Instructions

Generate a complete, ready-to-save AI-crawler-aware robots.txt for a website. Fetches the existing robots.txt (if any) and returns the finished file in generated.robotsTxt — the existing rules with an AI-crawler policy section merged in — plus the per-bot allow/block breakdown. Presets: 'allow-all' (every AI crawler allowed), 'recommended' (blocks only the training-only crawlers; everything that feeds AI search and answers stays allowed), 'search-only' (allows only the crawlers that feed AI search and answers, the ones the readiness score counts, and blocks the rest), 'block-all'. A file from 'recommended' or 'search-only' loses no points for crawler access. Write generated.robotsTxt to the site's /robots.txt. Requires an API key.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe website to generate a robots.txt for.
presetNoThe AI-crawler policy preset to apply.recommended

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only give readOnlyHint=false and openWorldHint=true; the description adds substantive context beyond them: it fetches the remote existing file, merges rules rather than replacing them, returns the result in a named field plus a per-bot breakdown, and requires an API key. It also correctly implies the tool does not itself write the file ('ready-to-save', 'Write generated.robotsTxt to the site's /robots.txt'), which is consistent with readOnlyHint=false being driven by the outbound fetch rather than a write.

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-loaded with the purpose and the return field, then the preset semantics. Dense but nearly every clause carries decision-relevant information; the only small excess is the presets being enumerated in a single run-on sentence, slightly hurting scannability.

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?

With no output schema, the description fully compensates by naming the return field, its shape (merged rules plus per-bot breakdown), and the caller's next action. Auth requirement and merge behavior are both covered, so an agent has everything needed to call and use the result.

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 baseline is 3; the description earns above that by giving real meaning to each enum value (what 'recommended' vs 'search-only' vs 'block-all' actually permit and how they affect scoring), which the one-line schema descriptions do not convey. The url parameter is left to the schema, which is acceptable given its coverage.

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?

Specific verb ('Generate') + specific resource ('robots.txt') with a clear qualifier ('AI-crawler-aware', 'ready-to-save'). It is easily distinguished from the sibling validate_robots (this one produces a file) and generate_llms_txt (different artifact), and it states upfront that an existing robots.txt is fetched and merged.

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?

The preset list functions as usage guidance: it names four policies and explains what each allows and blocks, plus the readiness-score consequence ('loses no points for crawler access'), which lets an agent pick a preset confidently. It does not explicitly say when to choose this tool over validate_robots or that the returned file must be written by the caller, but the context is clear.

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