Skip to main content
Glama

Publish Page

publish_page

Publish an HTML page to get a shareable URL with an optional title and automatic expiry timestamp. Use it to share agent-generated HTML pages that are deleted automatically.

Instructions

Publish an HTML page and return its shareable URL.

Returns {url, id, expires_at}. title is optional — when omitted it is extracted from the HTML tag, or falls back to 'Untitled'. expires_at is an ISO-8601 timestamp indicating when the page will be automatically deleted.

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_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYes
titleNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 does a solid job: it discloses the return shape, the title fallback chain, and the important side effect that pages are automatically deleted at expires_at. It stops short of stating whether the page is publicly accessible, whether HTML is sanitized, size limits, or auth requirements for a mutation tool.

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?

Front-loaded with the outcome, followed by a compact return-shape line and one-line explanations of each behavioral fact; every sentence earns its place with 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?

For a simple two-parameter tool with an output schema already present, this covers the essentials; the remaining gap is publishing-side behavior such as permissions, visibility, and limits on the HTML payload.

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 0%, so the description must supply meaning. It fully explains the optional title parameter including the extraction and fallback behavior, but says nothing about the required html parameter's constraints (size, inline assets, scripts).

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?

"Publish an HTML page and return its shareable URL" states a specific verb+resource+outcome, and clearly separates it from siblings like list_pages and delete_page without needing the schema.

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 context is only implied by the name and the mention of automatic deletion at expires_at; there is no explicit 'use this when...' guidance, no mention of prerequisites, and no comparison or redirection to sibling tools.

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