plopino

Official

Overview Schema Source Related Servers Discussions Admin

Publish a local file or folder and get a link

publish_path

Publish a local file, directory, or zip to a public URL, preserving folder structure for linked assets. Share Word, Excel, Markdown, code, images, or video as viewable pages instead of downloadable files.

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

Name	Required	Description	Default
`path`	Yes	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.
`update_url`	No	A 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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Public link to the published page — give this to the user.
`note`	Yes	Human-readable status: created vs updated, and how long the page is kept.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.10Sep 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "note": {
+      "description": "Human-readable status: created vs updated, and how long the page is kept.",
+      "type": "string"
+    },
+    "url": {
+      "description": "Public link to the published page — give this to the user.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "note"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 14, 2026

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."

First observedv0.1.4Sep 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate non-readonly, open-world, non-idempotent, non-destructive. The description adds meaningful behavioral specifics beyond those: it discloses that updating a URL replaces content, that symbolic links are skipped, and that zips are unpacked server-side. This enriches the agent's understanding without contradicting 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 two paragraphs and somewhat lengthy, but every sentence serves a purpose: it covers directory publishing, supported file types, the PowerPoint limitation, and the update_url behavior. It is front-loaded with the core purpose and structured logically, though it could be trimmed slightly without losing value.

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 tool has an output schema, return values are not needed. The description covers edge cases (symlinks, zip unpacking), usage scenarios, and even the PowerPoint preview limitation. It is complete for an agent to know when and how to invoke the tool correctly.

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 the description does not need to compensate. The description adds context about document types (Word, Excel, Markdown render as pages) but this is use-case guidance rather than parameter semantics; the schema already documents the path and update_url behavior thoroughly. 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?

The description states a clear verb and resource: 'Publish a local file, a zip, or a whole directory to a public URL, preserving the directory structure.' It distinguishes itself from the sibling publish_page only implicitly (by describing its own scope) but does not explicitly name the alternative, so it loses a point for lack of direct differentiation.

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?

It provides concrete context for when to use it: 'Use this when the page needs sibling files... write them into a directory first, then publish that directory. It is also the way to share any document...' This is clear usage guidance but does not explicitly state when not to use it or mention the sibling tool as an alternative, so it falls short of a 5.

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

Deploy Server