Skip to main content
Glama
plopino

plopino

Official
by plopino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Publish a local file or folder and get a link

publish_path

Publish a local file or directory to a public URL, preserving structure. Use for sharing documents, images, or web pages with linked assets.

Instructions

Publish a local file, a zip, or a whole directory to a public URL, preserving the directory structure. Use this when the page needs sibling files (CSS, JS, images) — write them into a directory first, then publish that directory. It is also the way to share any document: Word (doc/docx), Excel (xls/xlsx) and Markdown render as readable pages, code and data files get syntax-highlighted previews, and images and video display inline — the recipient opens a link instead of downloading a file. (PowerPoint files publish and download fine but have no rendered preview.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to a file or directory on this machine. A directory is uploaded recursively with its structure preserved (symbolic links are skipped, so the upload cannot escape the directory); a zip archive is unpacked server-side.
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 / path / description
      Previous value: -"Absolute path to a file or directory on this machine."New value: +"Absolute path to a file or directory on this machine. A directory is uploaded recursively with its structure preserved (symbolic links are skipped, so the upload cannot escape the directory); a zip archive is unpacked server-side."
  2. First observedv0.1.4

TDQS

A4.4/5.0
Behavior5/5

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

The description discloses rich behavioral details beyond annotations: uploads to a public URL, recursive upload with symlink skipping, server-side zip unpacking, update behavior preserving links, token requirement for updates, and rendering behavior for different file types including the PowerPoint limitation. This fully compensates for the lack of safety annotations.

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 dense but earns its length: front-loaded with the core publish action, then use-case guidance, then rendering behaviors and limitations. Each clause adds useful information, though it could be slightly tightened by explicitly routing to publish_html for single-file HTML cases.

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?

Given the open-world nature, two parameters, and no output schema, the description covers what an agent needs: what to publish, when to use it, key file-type behaviors, update semantics, and limitations. Nothing essential for correct invocation or selection is missing.

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 input schema already documents path and update_url well. The description adds no new parameter-level semantics beyond what the schema provides, including the zip unpacking and link replacement behavior. Baseline 3 is appropriate.

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 states a specific verb ('publish') with a clear resource scope: local file, zip, or directory, and explicitly notes directory structure preservation. It differentiates from the sibling publish_html by emphasizing when sibling files are needed and by positioning itself as the general sharing path for many document types.

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 gives explicit guidance on when to use this tool, such as when a page needs CSS/JS/images or when sharing documents that should render readably. It does not explicitly name the sibling tool publish_html or state a when-not-to-use condition, but the context is clear enough for an agent to select it appropriately.

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