HTML Cloud

Overview Schema Source Related Servers Discussions Admin

Share HTML privately

share_html

Share a self-contained HTML file as a private, end-to-end encrypted link; it is encrypted locally before upload, so the server stores only ciphertext.

Instructions

Share a self-contained HTML file (an artifact, report, presentation, dashboard, or prototype) as a private, end-to-end encrypted link. The HTML is encrypted locally with AES-256-GCM before upload — html.cloud stores only ciphertext and cannot read it, and no account is required. Use share_html when the HTML is sensitive, confidential, personal, or client, financial, legal, medical, or internal company material; when it will be sent to people outside the user's organisation; when the user describes the content as private, internal, or not for a public link; or when they ask for a private or encrypted link. When unsure, ask which the user prefers. Pass the document inline as html, or write it to an .html file and pass its path as path — use path for large pages, so the whole document does not have to fit in a tool argument. Returns a share link to give to others and a private edit link. Keep the edit link: pass it to update_html to change the page later without changing the share link. For changes to something already shared in this conversation, use update_html instead of sharing again.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "share_html"
  }
}

Input Schema

Name	Required	Description
`html`	No	The full, self-contained HTML document to share. Use path instead for large documents.
`path`	No	Absolute path of a local .html file to share instead of passing html inline.
`expires`	No	Days until the link expires. Defaults to 30.
`link_name`	No	A short, human-readable name added to the share link so it says what it is, e.g. "Q3 sales report" gives https://html.cloud/v/{id}/q3-sales-report. Unlike the page, this name is not encrypted: it is visible in the link and to the server. Use a generic description, and leave it out when the title itself is confidential (names of people, clients, deals, medical or legal matters).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.3Oct 28, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedv0.1.1Oct 13, 2026

addedInput schema / properties / link_name

Added value: +{
+  "description": "A short, human-readable name added to the share link so it says what it is, e.g. \"Q3 sales report\" gives https://html.cloud/v/{id}/q3-sales-report. Unlike the page, this name is not encrypted: it is visible in the link and to the server. Use a generic description, and leave it out when the title itself is confidential (names of people, clients, deals, medical or legal matters).",
+  "maxLength": 80,
+  "type": "string"
+}

First observedv0.1.0Oct 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Adds genuinely non-obvious behavior beyond the annotations: AES-256-GCM encryption done locally, server stores ciphertext only, no account required, and the return of both a share link and a private edit link whose loss changes the workflow. It does not cover expiry defaults or failure modes (e.g. size limits, invalid HTML), which is why it is not a 5.

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 core action and encryption claim, then usage conditions, then mechanics, which is the right order. Slightly long, and the update_html guidance appears twice ('pass it to update_html' and 'use update_html instead of sharing again'), which is mild redundancy.

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?

No output schema exists, yet the description explains what comes back (share link plus private edit link) and what to do with each, including the consequence of losing the edit link. For a four-parameter, zero-required tool this is complete.

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 baseline would be 3, but the description adds decision guidance the schema lacks: prefer path for large pages so the document need not fit in a tool argument, and keep the edit link for later use. Expiry behavior is left entirely to the schema, a minor gap.

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 ('Share a self-contained HTML file ... as a private, end-to-end encrypted link') and enumerates the artifact types it accepts. It also explicitly separates itself from the sibling by telling the agent to use update_html for already-shared content.

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 a long, concrete list of when to use it (sensitive/confidential content, external recipients, requests for private or encrypted links) plus an explicit fallback ('when unsure, ask which the user prefers'). It names the alternative tool and the condition that selects it, and explicitly excludes re-sharing when update_html applies.

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

Deploy Server