Skip to main content
Glama
Sign In
HTML Cloud

HTML Cloud

by ninjami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Update a shared HTML page

update_html
DestructiveIdempotent

Replace the content of an HTML page shared earlier using its private edit link. The existing share link stays the same, so recipients see the updated, locally encrypted version.

Instructions

Replace the content of an HTML page that was already shared with share_html, using its private edit link. The share link stays exactly the same, so anyone who already has it sees the new version. The new HTML is encrypted locally with the same key as before; html.cloud never sees the content. Use this when the user asks to change, fix, revise, or add to a page you shared earlier in the conversation — pass the full updated HTML document, not a diff: inline as html, or as the path of an .html file as path. Use path for large pages; do not fall back to share_html if the document is too big to pass inline.

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": {
      "edit_link": "<edit_link>"
    },
    "name": "update_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNoThe complete, self-contained HTML document that replaces the current one. Use path instead for large documents.
pathNoAbsolute path of a local .html file whose content replaces the current page, instead of passing html inline.
edit_linkYesThe private edit link returned by share_html (https://html.cloud/e/{id}#{key}).
link_nameNoThe link_name given to share_html for this page, if any, so the returned share link matches the one already handed out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.3
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / link_name
      Added value: +{
+  "description": "The link_name given to share_html for this page, if any, so the returned share link matches the one already handed out.",
+  "maxLength": 80,
+  "type": "string"
+}
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare this a destructive, idempotent, open-world write; the description earns credit beyond that by disclosing that the share link is stable, that content is encrypted locally with the previous key, and that html.cloud never sees it. It stops short of covering failure modes (expired/invalid edit_link, size ceilings) that matter for a destructive replace. No contradiction with the annotations.

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?

Front-loaded with the mutation and the link-stability consequence, then moves to usage conditions. Slightly padded by restating the path-for-large-pages rule twice (mid-sentence and again in the closing clause).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, four-parameter mutation with no output schema, the definition covers what is replaced, what is preserved (the share link), privacy behavior, payload form, and how link_name reconciles the returned link. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so section 3 baseline applies, but the description adds real semantics: pass the full document, not a diff, and prefer path for large pages. The large-page advice partly duplicates the schema's own 'Use path instead for large documents' wording, which caps it below 5.

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 content of an HTML page') and anchors it to the sibling that created the page ('already shared with share_html'). The scope difference from share_html is explicit, so an agent can pick between them without opening a schema.

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?

Gives an explicit trigger ('when the user asks to change, fix, revise, or add to a page you shared earlier in the conversation') and an explicit anti-pattern ('do not fall back to share_html if the document is too big to pass inline'), plus the html-vs-path routing rule. 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.

Deploy Server

Other Tools