Skip to main content
Glama

Publish to Flowershow

publish
Destructive

Publish files as a live website on Flowershow and get a shareable URL. Use when the user says "publish this", "put this online", "make this a website", "share this as a page" or "host this".

Accepts Markdown (.md, rendered as a styled page with navigation), HTML (.html, served as-is) and supporting files such as CSS, JS, JSON and images: one page or a small site, up to 50 files and 3 MB per call. Name the home page index.md or index.html.

Anyone with the link can see what you publish. When you publish, tell the user every path you are sending (and any paths in delete) and which site they go to: a new site, or the one being updated. Stop and ask before calling publish only when it matters: a file looks private or sensitive (drafts, personal notes, keys or passwords, data with people's names or emails), the call removes files (with delete or replaceWholeSite) the user didn't ask to remove, it would create a new site when the user meant to update one, or the set of files differs from what the user asked to publish. If the user already named the files, asked for the removal or said to go ahead, that is their yes.

Without an account this creates a new site that expires in 7 days and returns a claim link: always show the user the live URL and the claim link exactly as returned, so they can keep the site. To update that site later in the conversation, call publish again with its siteId and claimToken and only the files you changed or added: files you don't send are kept as they are. To remove pages or files, list their paths in delete (files can then be empty). Only when the user explicitly asks to start the site over, set replaceWholeSite to true: the files you send become the whole site and every other file is removed. If that would remove existing files, the call is refused and tells you how many and which; ask the user, then call again with confirmDeleteCount set to that number.

To keep a site in the user's Flowershow account, call claim-site; to work with sites already in their account, use list-sites, list-files and read-file. Those tools ask the user to sign in to Flowershow first; after that, publish goes into their account.

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": {
      "files": "<files>"
    },
    "name": "publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesFiles to add or update. When updating a site, send only the files that changed; other files are kept. Can be empty when only deleting.
deleteNoPaths of existing files to remove from the site (with siteId), e.g. ["old-page.md"]
siteIdNoUpdate this existing site instead of creating a new one
claimTokenNoThe claimToken returned when the anonymous site was created (needed with siteId when not signed in)
replaceWholeSiteNoSet true only when the user asks to start the site over: the files sent become the whole site and all other files are permanently removed. Never use it to update a few pages. Default false.
confirmDeleteCountNoWith replaceWholeSite: the number of existing files the replace will remove, as reported by the refused first call. Set it only after the user has confirmed.

Output Schema

NameRequiredDescriptionDefault
siteIdYes
liveUrlYes
messageYes
claimUrlNo
expiresAtNo
claimTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / confirmDeleteCount
      Added value: +{
      +  "description": "With replaceWholeSite: the number of existing files the replace will remove, as reported by the refused first call. Set it only after the user has confirmed.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / delete
      Added value: +{
      +  "description": "Paths of existing files to remove from the site (with siteId), e.g. [\"old-page.md\"]",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 1000,
      +  "type": "array"
      +}
    • changedInput schema / properties / files / description
      Previous value: -"The complete set of site files"New value: +"Files to add or update. When updating a site, send only the files that changed; other files are kept. Can be empty when only deleting."
    • addedInput schema / properties / replaceWholeSite
      Added value: +{
      +  "description": "Set true only when the user asks to start the site over: the files sent become the whole site and all other files are permanently removed. Never use it to update a few pages. Default false.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds the consequences: published content is publicly visible to anyone with the link, anonymous sites expire in 7 days and return a claim link, omitted files are preserved on update, and replaceWholeSite is refused with a file count until confirmDeleteCount is supplied. That is substantive behavior well beyond the annotation flags.

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?

Purpose and trigger phrases are front-loaded, followed by argument semantics and then the escalation/auth flow, which is the right order. It is long and dense, with a few sentences that could be tightened (the confirm-loop and claim-link instructions overlap slightly), but nothing is 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 destructive, open-world publish tool, the description covers public visibility, expiry, claiming, update-vs-create semantics, deletion, and the refusal/confirm error path. Return values are covered by the output schema, so no gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3; the description goes further by explaining that files should contain only changed or added paths on update, that files may be empty when only deleting, that siteId and claimToken pair together for anonymous updates, and that confirmDeleteCount must come from the refused first call. It leaves minor details (base64 vs text handling, path formatting) to the schema.

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?

Opens with a specific verb, resource and outcome: publish files as a live website and get a shareable URL. It names the sibling tools (claim-site, list-sites, list-files, read-file) and what each is for, so the agent can distinguish this tool from the rest of the set without opening schemas.

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?

Gives explicit trigger phrases ('publish this', 'put this online', 'host this') and a precise when-to-stop-and-ask rule list (private-looking files, unrequested removals, wrong site creation, file-set mismatch), plus the counter-rule that an explicit user request already constitutes consent. It also routes to alternatives for claiming and for account-site workflows.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.