Skip to main content
Glama
plopino

plopino

Official
by plopino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Publish an HTML page and get a link

publish_html

Publish an HTML page to a public URL for sharing on any device. Turn generated dashboards, reports, or charts into a link without requiring an account or configuration.

Instructions

Publish an HTML page to a public URL. Use this whenever the user asks to share, send, publish, or "give me a link to" a page — for example a dashboard, report, chart, or interactive page you just generated. Returns a public link that opens on any device; no account or configuration needed. Anonymous pages are kept for a month — with a token, storage is permanent and the page can be updated in place. Prefer this over telling the user to save the file and upload it somewhere themselves.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlYesThe complete HTML document to publish, including the <html> tag. It must be self-contained: relative references to local files will not resolve — use publish_path when the page needs sibling files (CSS, JS, images).
update_urlNoA URL returned by an earlier publish. When given, the content of that page is replaced and the link stays the same. Requires the server to be configured with a Plopino token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / html / description
      Previous value: -"The complete HTML document to publish, including the <html> tag."New value: +"The complete HTML document to publish, including the <html> tag. It must be self-contained: relative references to local files will not resolve — use publish_path when the page needs sibling files (CSS, JS, images)."
  2. First observedv0.1.4

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behaviors: pages are public, kept for a month anonymously, permanent with a token, and can be updated in place. This adds meaningful context about retention, access, and update semantics that the annotations do not convey.

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?

The description is front-loaded with the core action and usage trigger, then provides behavioral details and a clear alternative. It is moderately long but every sentence carries useful information without redundancy or filler.

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 two-parameter tool with no output schema, the description is complete: it states what it returns (a public link), when to use it, behavior details, and how to handle the main limitation (relative references). The lack of an output schema is not a gap because the return value is clearly described.

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 both parameters. The description adds value by emphasizing self-containment and the publish_path alternative, but it largely restates schema content rather than providing new parameter-level meaning.

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?

The description clearly states the tool publishes an HTML page to a public URL, with a specific verb and resource. It also distinguishes itself from the sibling publish_path by explicitly noting when publish_path should be used for pages needing sibling files.

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?

The description gives explicit when-to-use conditions ('whenever the user asks to share, send, publish, or give me a link'), and an explicit alternative ('use publish_path when the page needs sibling files'). It also discourages an inferior approach, telling the user to upload files manually, which fully guides tool selection.

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