Skip to main content
Glama
mysleekdesigns

CrawlForge MCP Server

by mysleekdesigns
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

generate_llms_txt

Read-onlyIdempotent

Generates an llms.txt file for a website, creating the standard that helps AI models understand and interact with site content for improved AI discoverability.

Instructions

Use this to generate an llms.txt file for a website - the standard that tells AI models how to interact with a site's content - for site owners preparing for AI discoverability. Not for reading a site's existing llms.txt (fetch_url on /llms.txt). Cost: 5 credits. Example: generate_llms_txt({url: "https://example.com"})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe website URL to generate llms.txt for
formatNoOutput format: llms.txt, llms-full.txt, or bothboth
outputOptionsNoOutput customization and organization details
analysisOptionsNoWebsite analysis options for depth, scope, and detection
complianceLevelNoCompliance level for generated guidelinesstandard

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv6.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / analysisOptions / additionalProperties
      Removed value: -false
    • removedInput schema / properties / outputOptions / additionalProperties
      Removed value: -false
    • addedInput schema / properties / outputOptions / properties / contactEmail / pattern
      Added value: +"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed4 schema fields changedv5.0.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / analysisOptions / properties / checkSecurity / default
      Previous value: -trueNew value: +false
    • addedInput schema / properties / analysisOptions / properties / probeRateLimit
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
    • addedInput schema / properties / outputOptions / properties / robotsStyle
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  3. First observedv4.10.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already carry readOnly/idempotent/non-destructive hints; the description adds the 5-credit cost and an example but does not disclose that the tool will fetch/analyze the target website or what 'generate' returns. No contradiction with annotations.

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 compact and front-loaded: purpose, exclusion/alternative, cost, and example are delivered in three sentences with no filler.

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?

For a tool with nested options and no output schema, the description still covers the core decision and invocation. It could more explicitly state that the tool crawls/analyzes the site and what the result payload looks like, but the cost, example, and annotation-provided safety profile make it sufficiently 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 parameter meaning is already documented. The description only gives a url example and adds no semantics for format, outputOptions, analysisOptions, or complianceLevel 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?

The description opens with a concrete verb and resource ('generate an llms.txt file for a website'), explains the standard and audience, and explicitly says what it is not for, differentiating it from fetch_url on /llms.txt.

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?

'Use this to generate...' and 'Not for reading... (fetch_url on /llms.txt)' give direct when/when-not guidance with the alternative named. The 5-credit cost and minimal invocation example also reinforce appropriate use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mysleekdesigns/crawlforge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server