SEO Score API

Generate llms.txt

llms_txt

Read-onlyIdempotent

Generate an llms.txt file for a domain and return its text, ready to save at /llms.txt. Basic plan ($15/mo) and higher get the curated version with per-page descriptions; other keys (or no key) get the basic version.

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": {
      "domain": "<domain>"
    },
    "name": "llms_txt"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Bare domain without protocol or path, e.g. example.com.

Output Schema

Name	Required	Description	Default
`llms_txt`	No	The generated llms.txt file text.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive, so the bar is lower. The description adds genuinely new behavior: the call returns the file text rather than writing it, and the output tier depends on the API key's plan (curated with per-page descriptions on Basic+ at $15/mo, basic otherwise) — information absent from annotations and important for interpreting results.

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?

Two sentences with zero waste: the primary action and artifact location come first, the plan-dependent output variation second. Nothing is repeated from the title or schema.

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-parameter, read-only generator with an output schema, the description covers action, return artifact, save location, and the plan-driven difference in output richness. Nothing an agent needs to call it correctly or interpret the result is missing.

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 coverage is 100% and the single parameter's description already specifies 'bare domain without protocol or path, e.g. example.com,' matching the description's use of 'for a domain.' The description adds no format, normalization, or failure semantics beyond the schema, so baseline 3 applies.

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?

States a specific verb (generate) and resource (llms.txt for a domain) plus the outcome (its text, ready to save at /llms.txt). No sibling tool in the catalog produces an llms.txt file, so the resource alone distinguishes it from audits, backlinks, and citation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the resource itself — an agent needing an llms.txt file knows this is the tool. But there is no explicit when-to-use guidance, no conditions or exclusions, and no pointer to any alternative for related needs such as ai_readability or ai_readability-style checks.

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

All SEO Score API tools Inspect

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.