Skip to main content
Glama
Sign In
ai-visibility-mcp

ai-visibility-mcp

by tsushanth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

generate_llms_txt

Generate an llms.txt line and a content pack with ownable phrase, meta description, and FAQ block for a product to boost visibility to AI answer engines.

Instructions

Generate an llms.txt line plus a content pack (ownable phrase, llms.txt sentence, meta description, FAQ block) for a product, ready to hand-place on a landing page or drop as a file. Does not write files or touch git — pure text generation.

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": {
      "name": "<name>",
      "description": "<description>",
      "url": "<url>"
    },
    "name": "generate_llms_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical URL
nameYesProduct name
phraseNoOwnable niche phrase to anchor on, e.g. "one-click autofill for Greenhouse, Lever, and Ashby job applications". If omitted, only llms.txt is generated (no content pack).
descriptionYesOne-sentence plain description of what it does

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Since no annotations are provided, the description carries the burden of behavioral transparency. It clearly states that the tool is pure text generation (no file writing, no git interaction), which is helpful. However, it doesn't disclose potential limits, response format, or whether generation is deterministic or uses external services.

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 two sentences with no wasted words. It front-loads the main purpose, specifies the output components, and clarifies constraints in a concise manner.

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?

Given the tool has 4 parameters with 100% schema coverage, no output schema, and no annotations, the description provides a clear functional overview. However, it could be more complete by mentioning that the output includes the generated text (since no output schema exists) and whether the FAQ block is a fixed format or customizable.

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 description coverage is 100%, so the baseline is 3. The description adds value by explaining that the 'phrase' parameter is optional and that omitting it triggers only llms.txt generation (no content pack), which is not stated in the schema. This clarifies behavior 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 clearly states the tool generates an llms.txt line plus a content pack (ownable phrase, llms.txt sentence, meta description, FAQ block) for a product, distinguishing it from siblings like check_visibility and cloudflare_ai_bot_audit by focusing on text generation for SEO/content, not visibility checks or bot audits.

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 description specifies when to use the tool (to generate content for a landing page or file drop) and what it does not do (does not write files or touch git), providing clear context. However, it doesn't explicitly exclude alternatives or mention when not to use this tool versus other content generation tools.

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

Deploy Server

Other Tools