Skip to main content
Glama

Write AI visibility files for a site

generate_ai_fix_files
Read-onlyIdempotent

Write the files that help AI assistants understand a site, from the site's own live pages: an llms.txt map of the key pages (titles and descriptions as published), Organization and WebSite JSON-LD (name, logo, profile links found on the homepage), FAQPage JSON-LD for FAQs the pages already show, robots.txt lines only when a change is needed, and per-page fixes (missing titles, descriptions, H1, pages empty without JavaScript). Use this when someone asks for an llms.txt, schema markup, or "make my site AI ready"; in a code editor, apply the result in the site's code. Prices are never guessed.

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

Input Schema

NameRequiredDescriptionDefault
domainYesWebsite domain, for example example.com

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive. The description adds genuine value beyond them: inputs come from the site's own live pages, robots lines are emitted 'only when a change is needed,' and 'Prices are never guessed.' The 'apply the result in the site's code' clause reconciles the 'Write' naming with readOnlyHint by clarifying the agent must deploy the output itself.

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 core action, then a dense but purposeful enumeration of outputs and a usage sentence. Every clause (visible-JS note, prices-never-guessed, apply-in-editor) carries information, though the single run-on sentence is heavy and could be split for scanability.

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?

With an output schema present, the description needn't explain return values, and it still enumerates the produced artifacts and the read-only-source behavior. Given one documented parameter and rich annotations, an agent has what it needs to call correctly; the only missing piece is explicit sibling routing.

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 only one parameter (domain) exists, fully documented in the schema. The description adds no format or constraint detail beyond the schema, so it neither compensates nor detracts — baseline 3 for a fully documented single param.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Write the files that help AI assistants understand a site') and enumerates concrete outputs (llms.txt, Organization/WebSite JSON-LD, FAQPage JSON-LD, robots.txt lines, per-page fixes). This is far more specific than a generic 'generate' tool. However, it never differentiates from siblings like generate_ai_robots_rules or audit_page_for_ai, whose scope overlaps with the robots.txt and per-page-fix outputs described here.

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?

Clear usage context: 'Use this when someone asks for an llms.txt, schema markup, or "make my site AI ready"' plus the crucial note that 'in a code editor, apply the result in the site's code.' That gives a real trigger and clarifies the tool generates rather than deploys. It stops short of naming alternatives (e.g., generate_ai_robots_rules for robots-only cases).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources