host-html

Update a published page in place

update_page

Replace the HTML of a page you already published, keeping the SAME link. Use this for every revision — a fix, a new draft, refreshed numbers — instead of publishing a new page, so a link the user already shared keeps working. Only pages owned by the same account can be updated.

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": {
      "slug": "<slug>",
      "html": "<html>"
    },
    "name": "update_page"
  }
}

Input Schema

Name	Required	Description	Default
`html`	Yes	The full, self-contained replacement HTML document.
`slug`	Yes	The page's slug (the part after /p/), or its full URL.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full load and does disclose the key traits: it is an in-place overwrite, the URL is preserved, and there is an ownership precondition ('Only pages owned by the same account can be updated'). It stops short of saying whether prior HTML is recoverable, what happens on a slug mismatch, or how the response looks.

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, zero filler. The core action and the same-link guarantee are front-loaded, and the routing rationale follows.

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?

For a 2-parameter mutation tool with no annotations and no output schema, the definition covers purpose, alternative, and the ownership restriction. It omits failure modes (slug not found, not the owner) and recoverability of overwritten content, which are the remaining gaps an agent might need.

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 description coverage is 100%, so both parameters are already documented. The description only adds that the slug corresponds to the link that stays constant; it gives no extra format or edge-case detail for slug resolution or html size constraints, 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 and resource ('Replace the HTML of a page you already published') plus the defining constraint 'keeping the SAME link.' This is immediately distinguishable from publish_html, which by implication creates a new page/link.

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?

Explicitly routes revisions here ('a fix, a new draft, refreshed numbers') and names the alternative behavior to avoid ('instead of publishing a new page'), with the reason (a shared link keeps working). Both when-to-use and when-not-to-use are covered.

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

All host-html tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.