Skip to main content
Glama

llms.txt Generator

by de.llms-txt-generator
OverviewDiscussionsAdmin

Generate llms.txt for a website

generate_llms_txt
Read-onlyIdempotent

Use this when the user wants a new llms.txt file for a public website they name. Reads up to 15 public HTML pages of that one domain (start page, XML sitemap, internal links) and returns a ready-to-publish llms.txt draft in Markdown, plus a format validation score, the Lighthouse "Agentic Browsing" result, the status of any llms.txt already published on the site, and the URLs that were left out with the reason. Deterministic: no language model is involved, every title and description is taken from the pages themselves. Limitations: honors robots.txt and stops if the start page is disallowed; does not render JavaScript, does not log in, and does not follow links to other domains; one request can take up to about a minute. Do not use this to fetch arbitrary page content or for sites the user only mentions in passing. Result messages are in German.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe website, as a bare domain or full URL, e.g. "example.com" or "https://www.example.com".
maxPagesNoUpper limit of pages to read. Default 15.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
excludedYes
finalUrlYes
llmsTextYesThe complete llms.txt draft in Markdown.
maxPagesNo
siteNameNo
warningsYes
pageCountYes
lighthouseYesResult of the three Lighthouse 13.3 "llms-txt" audit rules.
validationYesFormat check against the llmstxt.org proposal.
limitReachedYestrue when the page limit stopped the crawl.
publishedFileNoStatus of the llms.txt currently published on the site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / maxPages / description
      Previous value: -"Obergrenze der Seiten, Standard 15."New value: +"Upper limit of pages to read. Default 15."
    • changedInput schema / properties / url / description
      Previous value: -"Website, z. B. \"beispiel.de\" oder \"https://www.beispiel.de\"."New value: +"The website, as a bare domain or full URL, e.g. \"example.com\" or \"https://www.example.com\"."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "excluded": {
+      "items": {
+        "properties": {
+          "reason": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url",
+          "reason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "finalUrl": {
+      "type": "string"
+    },
+    "lighthouse": {
+      "description": "Result of the three Lighthouse 13.3 \"llms-txt\" audit rules.",
+      "properties": {
+        "checks": {
+          "items": {
+            "properties": {
+              "failureMessage": {
+                "type": "string"
+              },
+              "id": {
+                "enum": [
+                  "h1",
+                  "links",
+                  "length"
+                ],
+                "type": "string"
+              },
+              "label": {
+                "type": "string"
+              },
+              "passed": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "id",
+              "passed"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "passed": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "passed",
+        "checks"
+      ],
+      "type": "object"
+    },
+    "limitReached": {
+      "description": "true when the page limit stopped the crawl.",
+      "type": "boolean"
+    },
+    "llmsText": {
+      "description": "The complete llms.txt draft in Markdown.",
+      "type": "string"
+    },
+    "maxPages": {
+      "type": "integer"
+    },
+    "note": {
+      "type": "string"
+    },
+    "pageCount": {
+      "type": "integer"
+    },
+    "publishedFile": {
+      "description": "Status of the llms.txt currently published on the site.",
+      "type": "object"
+    },
+    "siteName": {
+      "type": "string"
+    },
+    "validation": {
+      "description": "Format check against the llmstxt.org proposal.",
+      "properties": {
+        "byteSize": {
+          "type": "number"
+        },
+        "issues": {
+          "items": {
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "line": {
+                "type": "number"
+              },
+              "message": {
+                "type": "string"
+              },
+              "severity": {
+                "enum": [
+                  "error",
+                  "warning",
+                  "info"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "code",
+              "severity",
+              "message"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "links": {
+          "type": "number"
+        },
+        "score": {
+          "maximum": 100,
+          "minimum": 0,
+          "type": "number"
+        },
+        "valid": {
+          "description": "true when no error-level finding exists.",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "valid",
+        "score",
+        "issues"
+      ],
+      "type": "object"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "llmsText",
+    "finalUrl",
+    "pageCount",
+    "limitReached",
+    "validation",
+    "lighthouse",
+    "excluded",
+    "warnings"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description goes well beyond them: deterministic/no LLM, 15-page cap, robots.txt honoring, no JS rendering, no login, no cross-domain following, ~1 minute latency, and German result messages. These are exactly the operational facts an agent cannot get from the 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?

Front-loaded with the trigger condition, then outputs, then constraints. Every sentence carries distinct information — the deterministic note, the limitations list, and the anti-use cases all earn their place for a tool with this much behavior.

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?

For a one-shot generation tool with an output schema already present, the description supplies everything else an agent needs: scope, page budget, runtime, language of results, and failure conditions (robots.txt denial). Nothing material is missing.

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 the baseline is 3; the description adds value by clarifying that only the named domain is read, that the page budget defaults to 15, and that it is spent on the start page, XML sitemap, and internal links. It does not restate the bare-domain-vs-URL syntax beyond what the schema already documents.

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 definition names a specific verb and artifact (generate an llms.txt draft) scoped to 'a public website they name', and it distinguishes itself from the check_* / validate_* siblings by stating it produces a new file rather than inspecting an existing one. The outputs are enumerated explicitly (draft, validation score, Lighthouse result, published-file status, skipped URLs).

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?

It opens with the triggering condition ('when the user wants a new llms.txt file for a public website they name') and closes with explicit exclusions ('Do not use this to fetch arbitrary page content or for sites the user only mentions in passing'). The boundary against the sibling check/validate tools is implicit but clear from the 'new file' framing.

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

All llms.txt Generator toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources