Skip to main content
Glama

Publish site HTML

update_site
Idempotent

Replaces the site's index.html with the given full HTML and publishes it immediately. The previous version is kept in the version history (last 10), so it can be restored. When several people edit the site, pass expected_version (the version from get_site): if someone saved in the meantime, nothing is overwritten and you get a version_conflict error.

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

Input Schema

NameRequiredDescriptionDefault
htmlYesFull HTML of the page (max 5 MB).
siteYesSite id or name, e.g. "my-portfolio" or "my-portfolio.hostilo.page" (from list_sites).
expected_versionNoOptional: the version from get_site. If the site was saved by someone else since then, nothing is published and you get a version_conflict error (get the site again and merge).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site / description
      Previous value: -"Site id or name, e.g. \"my-portfolio\" or \"my-portfolio.hostilo.app\" (from list_sites)."New value: +"Site id or name, e.g. \"my-portfolio\" or \"my-portfolio.hostilo.page\" (from list_sites)."
  2. Changed1 schema field changed
    • addedInput schema / properties / expected_version
      Added value: +{
      +  "description": "Optional: the version from get_site. If the site was saved by someone else since then, nothing is published and you get a version_conflict error (get the site again and merge).",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: publication is immediate, the previous version is retained in version history (last 10) and restorable, and a stale expected_version results in nothing being overwritten. This directly clarifies the mutation's reversibility and conflict safety, which the destructiveHint/idempotentHint flags alone do not convey. The described behavior is consistent with destructiveHint=false because prior content remains recoverable.

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?

Three sentences, each earning its place: the core action first, then the recoverability guarantee, then the concurrency caveat. No redundant restatement of the title or schema and no filler.

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?

There is no output schema, and the description partially compensates by naming the version_conflict error, but it does not say what a successful call returns (for example, the new version id). For a mutation tool with 100% schema coverage this is close to complete, with only the success return value left unspecified.

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%, and the schema already explains html (full page, max 5 MB), site (id or name from list_sites), and expected_version (conflict semantics). The description restates the expected_version conflict flow but adds no format or syntax detail beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource: "Replaces the site's index.html with the given full HTML and publishes it immediately." An agent can distinguish this from create_site and restore_version by the replace-and-publish action. It stops short of naming publish_files, the closest sibling, so the boundary between single-file replacement and multi-file publishing is left implicit.

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?

Gives concrete when-to-use guidance for the optional expected_version parameter: pass it when several people edit the site, using the version from get_site. It also explains the resulting behavior (version_conflict error) when the version is stale. It provides no exclusions against siblings like publish_files or import_zip, so full routing guidance is incomplete.

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.