Skip to main content
Glama

Publish the draft

publish_site
DestructiveIdempotent

Publishes the current draft so anyone can see it at the site's web address. expected_draft_version, from get_site, stops a change made elsewhere from being published by mistake.

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": {
      "site_id": "<site_id>"
    },
    "name": "publish_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site id from list_sites or create_site.
expected_draft_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description's real addition is public visibility ("anyone can see it"), which puts this write in front of an external audience. It does not say what the publish overwrites or how a stale expected_draft_version fails.

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?

Two sentences, front-loaded with the effect, zero filler. The concurrency note reads as a slightly awkward interjection, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain the result. It does not say what a version-conflict failure looks like or whether the live site's previous state is replaced. For an open-world destructive write, that is a material gap.

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 50%: site_id is described in the schema as "The site id from list_sites or create_site" while expected_draft_version has no schema description. The prose notes where expected_draft_version comes from ("from get_site"), but most of its meaning beyond that name now sits in the failed semantic baseline, and the description does not explain the error behavior. Baseline 3 applies when the schema handles part of the load and the prose adds only a partial assist.

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?

States a specific verb+resource pair ("Publishes the current draft") and adds the observable effect ("so anyone can see it at the site's web address"), which separates it from read tools like get_site and from the implied opposite, unpublish_site. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

Gives a clear condition for use (publishing the current draft) and the reason to pass expected_draft_version, which functions as guidance against unconditional publishing. It offers no explicit when-not case, no preconditions, and never contrasts the choice with unpublish_site or list_versions.

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