Skip to main content
Glama

Write page

write_page
Destructive

Create or replace an HTML page in the draft. Path "index.html" (or "/") is the home page; "about" becomes about.html served at /about.

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>",
      "path": "<path>",
      "html": "<html>"
    },
    "name": "write_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesComplete HTML document
pathYes
siteYesSite slug (e.g. "kopitiam-muar") or id
expected_revisionNoRevision from read_page; the save is refused if the file changed since. "new" = must not exist yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description explicitly states that the modification happens 'in the draft,' which is a crucial behavioral constraint regarding live site safety. This adds value beyond the provided annotations by explaining the nature of the environment in which the change occurs.

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 a single, highly effective sentence that conveys the core utility, lifecycle, and naming conventions without any unnecessary filler or verbose formatting.

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 its scope as a web page manipulation tool, it provides enough detail regarding path conventions and the 'draft' state. The combination of description and the destructive hint allows a model to use it correctly while being cautious about its impact on live data.

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?

With 75% schema coverage, the description fulfills the minimum requirement for parameter semantics. It focuses on the 'path' and the resultant file, which maps directly to the schema without adding new semantic information about the parameters themselves.

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 defines the function (Create or replace an HTML page) and specifies the resource being acted upon (a draft page). It is distinct from similar tools like write_file by focusing specifically on HTML page conventions and lifecycle.

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 tool defines its domain specifically as the HTML drafting phase and explains how paths are converted (e.g., 'about' to 'about.html' served at '/about'). While it doesn't explicitly mention sibling tools, it provides clear operational context.

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