Skip to main content
Glama

Publish HTML

publish_html

Publish an HTML page on HTMLpad and get a public link to share. Returns the link, a private edit link and an edit token. Free pads stay online for 90 days. Pages may not contain password or payment card fields.

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

Input Schema

NameRequiredDescriptionDefault
htmlYesA complete HTML document or fragment, up to 512 KB.
addressNoOptional address for the page, as in htmlpad.org/<address>/. Letters, numbers, dots, dashes or underscores, up to 64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the write, non-idempotent, open-world, non-destructive profile, and the description goes beyond them by naming the return artifacts (public link, private edit link, edit token) and the 90-day free-pad lifetime. The most security-relevant detail, that the edit token is a secret the caller must retain, is implied rather than stated, and no auth or rate-limit behavior is mentioned.

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 tight sentences, front-loaded with the action and its result before the constraints. No filler; each sentence carries either the outcome, the returned values, or a policy limit.

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 two-parameter write tool with annotations and no output schema, the description covers purpose, returns, expiry and content policy, which is nearly everything an agent needs. The one gap is that it never explains the relationship to update_pad, i.e. that publishing is a distinct create step rather than an edit.

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 coverage is 100%, so both parameters (html, address) are already fully documented in the schema, including size limit and allowed address characters. The description adds no syntax or format meaning beyond that, so the baseline 3 is appropriate.

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?

A specific verb ('Publish') plus resource ('an HTML page on HTMLpad') and the concrete outcome ('get a public link to share') make the action unmistakable. It does not explicitly contrast itself with get_pad or update_pad, so sibling differentiation is left to inference from the verbs.

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 description supplies real usage context: pages are subject to a content restriction (no password or payment-card fields) and free pads expire after 90 days, which tells an agent both what is permissible and what the lifetime is. It stops short of saying when to reach for publish_html versus update_pad on an existing pad.

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