Skip to main content
Glama

Veröffentlichen

publish
Destructive

Überträgt den Workspace auf das Publish-Ziel. IMMER zuerst mit dry_run=true aufrufen, das Ergebnis dem Kunden vorlegen und erst nach seiner Bestätigung echt veröffentlichen. Die Übertragung läuft im Hintergrund – der Stand kommt über publish_status. PHP läuft in der Vorschau auch ohne Paket (vollständig nur auf MADLAB-Hosting, sonst ohne Datenbereich und Netz); auf MADLAB-Hosting veröffentlichen lässt es sich nur mit dem Zusatzpaket «PHP» (website_list zeigt «+ PHP») – sonst weist publish ab und sagt warum. Ein Publish überträgt schrittweise (Medien, dann CSS/JS, dann HTML, Löschungen zuletzt): Ein Abbruch hinterlässt eine benutzbare Website, während des Laufs kann sie aber schon teilweise neu sein. Er ersetzt den ausgelieferten Stand vollständig und fasst den Datenbereich (/var/www/storage) nie an: Bestellungen, Uploads und Konfiguration einer PHP-Website bleiben.

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

Input Schema

NameRequiredDescriptionDefault
dry_runNoNur zeigen, was übertragen würde. Vorgabe: false.
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes far beyond readOnlyHint=false / destructiveHint=true: the transfer runs in the background, progresses incrementally (media, then CSS/JS, then HTML, deletions last), an abort leaves a usable though possibly partially updated site, and the delivered state is fully replaced. It also states an important safety boundary not covered by annotations: /var/www/storage is never touched, so orders, uploads and configuration persist.

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?

It is dense but front-loaded: the workflow, the background/status behavior, and the PHP edge case come in a sensible order, and every clause carries operational information. It is longer than most definitions, but only the PHP hosting caveat is genuinely detailed enough to slow reading.

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?

No output schema exists, so the description must convey the asynchronous behavior, and it does by pointing to publish_status. For a destructive publish tool, everything an agent needs is present: the required dry-run step, rejection conditions, interruption semantics, and what is preserved.

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 both parameters are documented. The description still adds real meaning to dry_run by making the dry-run-then-confirm sequence the mandatory first step rather than an optional flag, but it adds nothing beyond the schema for the website identifier.

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?

States a specific verb and resource: it transfers the workspace to the publish target, and it explicitly routes status checks to publish_status. The distinction from preview and rollback is implicit but clear from the described effect: it replaces the delivered state.

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 a strict workflow: always call first with dry_run=true, present the result to the customer, and only publish for real after confirmation. It also names a concrete exclusion condition – a PHP website on MADLAB hosting without the «PHP» add-on is rejected and website_list shows that – which no sibling name alone could convey.

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.

Resources