Skip to main content
Glama

publish_html

Publishes HTML or Markdown content as a shareable BrewPage URL for free no-signup hosting, with password protection, custom expiry, and optional filenames. Share the returned link.

Instructions

Publish HTML or Markdown content to BrewPage (repository default limit 5 MiB). Returns its primary share link and owner token. Supports password protection, custom TTL, optional filename, and an opt-in top toolbar (showTopBar). When deliveryMode is omitted for a public page, the server may publish it on its own subdomain if the page needs browser features a BrewPage link does not provide; the result then includes deliveryModeReason and a delivery notice. Markdown raw HTML is allowlisted: scripts, styles, event handlers, forms and embeds are removed. Always share the returned URL.

Input Schema

NameRequiredDescriptionDefault
formatNoContent format, default HTML. HTML or MARKDOWN; the server also maps aliases (md, text/markdown, file extensions, code languages) and detects unknown values from content, reporting the change in notices.HTML
contentYesHTML or Markdown content to publish
ttlDaysNoRequested TTL: days as a number, or a string such as '2w', '36h' or '1 month' (default 15 days). The server rounds to whole days and clamps to the allowed range (1-30 by default; owner caps differ), reporting each adjustment in notices; use returned expiresAt.
filenameNoOptional original filename (≤200 chars). Used as title fallback when no <title>/<h1>; immutable on update.
passwordNoOptional password to protect the page
namespaceNoOptional. Omit to generate an unlisted namespace: anyone with its unpassworded link can read it, but it is excluded from gallery/search. Pass a custom namespace to group unlisted content, or pass `public` ONLY when the user explicitly wants gallery/search eligibility. Password-protected content stays excluded; unlisted, protected or otherwise ineligible native responses carry noindex; eligible public HTML, sites and files may permit indexing.
showTopBarNoAdd a thin top toolbar (filename + Download button + theme toggle) on the served page. Default: hidden.
deliveryModeNoOptional delivery choice for a fresh publication, independent of password/namespace. Fresh sites and HTML-format pages outside public (including the default unlisted namespace) always use subdomain; an explicit path there still publishes, on subdomain, with a delivery notice. Everything else in any namespace (Markdown, code/text, files, JSON, KV, public HTML) defaults to path (Promotion); public HTML may automatically choose subdomain for browser features. When creation returns an existing publication, it keeps its actual mode and URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 burden and discloses useful behavior: returned share link and owner token, default 5 MiB limit, Markdown sanitization rules, automatic subdomain delivery behavior, and the notice fields returned when deliveryMode is auto-selected. It still omits auth/permission requirements and explicit create-vs-update semantics.

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?

The description is front-loaded with purpose and return values, then adds operational caveats. It is dense but each sentence contributes relevant information for an 8-parameter publishing tool.

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 complex tool with no output schema and no annotations, the description supplies return details (share link, owner token, deliveryModeReason, delivery notice), sanitization rules, size limit, and delivery-mode caveats. The main remaining gap is explicit routing guidance versus sibling publishing/update tools.

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 the schema already documents all 8 parameters thoroughly. The description restates high-level features (password, TTL, filename, showTopBar, deliveryMode) but adds little syntax or meaning beyond what the schema provides.

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?

The description states a specific verb and resource: 'Publish HTML or Markdown content to BrewPage'. It also names the return artifacts (share link and owner token). However, it does not explicitly distinguish this tool from siblings like publish_site, publish_file, or update_html.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the content type ('HTML or Markdown content'), and there is conditional guidance such as passing 'public' ONLY when gallery/search eligibility is explicitly wanted. But the description never states when to choose this tool over publish_site, publish_file, publish_json, or update_html.

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