Skip to main content
Glama

Publish site

site_publish
Destructive

Publish a site's code tree, now or as of an earlier change, at the site's address, replacing what is live there. Requires an admin of its home wiki or an organization owner. The result gives the url and the change that is live, and previous names what it replaced.

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": {
      "id": "<id>",
      "org": "<org>"
    },
    "name": "site_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe site's short name (its name lowercased, other characters made hyphens, e.g. deal-flow), or its client id.
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
changeIdNoPublish the tree as of this change, e.g. to roll back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations declare a destructive, non-read-only, open-world write; the description goes well beyond them by stating that live content is replaced, naming the permission requirements, and outlining the return payload (url, live change, and the 'previous' value that was replaced). That is exactly the extra context an agent needs before a destructive publish.

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?

Three dense sentences, front-loaded with the action and its effect, then auth requirements, then the result. Every sentence carries information, though the final sentence about return values is slightly verbose.

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?

With only three parameters and no output schema, the description covers the action, permissions, destructive effect, and result shape. Nothing an agent needs to invoke it correctly 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 coverage is 100%, so id, org, and changeId are already documented including the rollback hint on changeId. The description restates the 'now or earlier change' semantics and adds nothing new about org or the id/client-id format, so baseline 3 applies.

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 opens with a specific verb+resource ('Publish a site's code tree') and adds scope details — the site's address, immediate or historical change, and that it replaces live content. That clearly separates it from siblings like site_create or site_update, though no sibling is named explicitly.

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 gives concrete preconditions ('Requires an admin of its home wiki or an organization owner') and a use scenario for the optional parameter ('now or as of an earlier change', e.g. rolling back). It never states when not to use it or names an alternative tool, keeping it 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources