Skip to main content
Glama

Publish a local file or folder and get a link

publish_path

Publish a local file, zip, or directory to a public URL with preserved structure, so recipients can open links and view documents, images, code, and sibling assets inline.

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

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": {
      "path": "<path>"
    },
    "name": "publish_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to a file or directory on this machine. A directory is uploaded recursively with its structure preserved; symbolic links and common private paths (.git, .env*, node_modules, .ssh, .aws) are skipped. An explicitly selected single file is uploaded as requested, so never select credentials or other secrets. 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.

Output Schema

NameRequiredDescriptionDefault
urlYesPublic link to the published page — give this to the user.
noteYesHuman-readable status: created vs updated, and how long the page is kept.
claimUrlNoPrivate browser claim link for the publisher only. Never give it to page viewers or append it to the public URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / path / description
      Previous 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."New value: +"Absolute path to a file or directory on this machine. A directory is uploaded recursively with its structure preserved; symbolic links and common private paths (.git, .env*, node_modules, .ssh, .aws) are skipped. An explicitly selected single file is uploaded as requested, so never select credentials or other secrets. A zip archive is unpacked server-side."
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / properties / claimUrl
      Added value: +{
      +  "description": "Private browser claim link for the publisher only. Never give it to page viewers or append it to the public URL.",
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.1.10
    • 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"
      +}
  3. 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."
  4. First observedv0.1.4

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, destructiveHint=false and idempotentHint=false, but the description adds meaningful context beyond them: the output is a public URL (exposure implied), PowerPoint files publish without a rendered preview, and zip archives are unpacked. It does not describe what happens on a failed upload or whether a previously published link persists, which keeps it below a 5.

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 purpose and the primary usage rule are front-loaded in the first two sentences, with the file-type rendering details trailing as supporting context. The long enumerations of formats and the PowerPoint parenthetical are dense but each conveys a real capability, so little is wasted.

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?

With an output schema present, return values need no explanation, and 100% schema coverage handles parameter details. The only substantive hole is the absence of any comparison to publish_page, leaving the sibling choice unresolved from the description alone.

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 both parameters are already fully documented, and the baseline is 3. The description reinforces the directory-recursion behavior implied by 'path' but says nothing about the update_url parameter — the link-replacement workflow is only discoverable from the schema.

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 gives a specific verb+resource ('Publish a local file, a zip, or a whole directory to a public URL') and enumerates supported content types, so the agent knows exactly what it does. However, it never mentions the sibling publish_page, so an agent choosing between the two gets no disambiguation from this text.

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 states a clear triggering condition — 'Use this when the page needs sibling files (CSS, JS, images) — write them into a directory first, then publish that directory' — plus the sharing use case for documents and media. What's missing is an explicit exclusion or pointer to publish_page for the single-page case.

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