Skip to main content
Glama

WordPress: put the llms.txt live

wp_llms_txt_set
DestructiveIdempotent

Put a plain-text /llms.txt on a WordPress site (draft it with llms_txt_draft first). The Bridge stores the text and serves it at /llms.txt; no file is written to the server, a real llms.txt file on disk still wins, and the previous text is kept as a backup. Plain text only, 50,000 characters at most; an empty text removes it. Previews first; confirm to put it live. Needs Bridge 1.8.0+ and an administrator's application password.

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": {
      "site": "<site>",
      "text": "<text>"
    },
    "name": "wp_llms_txt_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
textYesThe whole llms.txt, as approved by the person; empty removes it
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real context beyond them: Bridge storage, no file written to disk, a real on-disk llms.txt still wins, previous text kept as backup, 50,000-char cap, Bridge 1.8.0+ and administrator application password required. It stops short of describing what the preview/live response reports.

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?

Purpose is front-loaded, then constraints and workflow in compact clauses; nearly every clause earns its place. The clipped 'Previews first; confirm to put it live' phrasing slightly reduces readability.

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?

Covers prerequisites, storage/precedence semantics, size limit, and the confirmation workflow for a 3-param mutation tool with no output schema. The one substantive gap is what 'site' accepts (ID, URL, or domain).

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 67% and text/confirm already carry schema descriptions including maxLength and preview semantics; the description largely restates these (50,000 limit, empty removes). The 'site' parameter is left undefined in both schema and description.

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?

Specific verb and resource ('Put a plain-text /llms.txt on a WordPress site'), plus explicit routing to the sibling llms_txt_draft for drafting. Clearly different from the wp_set_seo / wp_theme_option_set setters.

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?

States the prerequisite (draft with llms_txt_draft first), the gating rule ('Previews first; confirm to put it live'), and an exclusion ('an empty text removes it'). An agent knows the workflow order and when to flip confirm.

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.