Skip to main content
Glama

Pagetool

Make staged changes live

publish_staged

Makes a site's staged changes (edit_section/set_theme with stage: true) live. The live page is saved as a version first, so this can be undone with restore_version. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "publish_staged"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_keyNoThe site whose staged changes should go live. Defaults to the caller's current draft site when omitted.
draft_tokenNoThe draft token returned by draft_create, if you are working on an anonymous draft. Only needed when your client cannot send the x-pagetool-draft-token header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, but the description adds genuinely new context: a version snapshot is saved before the live page is overwritten, the change is undoable via restore_version, and the operation is free (no payment/credit path involved). This is consistent with destructiveHint=false. It stops short of saying what happens if nothing is staged or whether re-publishing twice creates two versions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action, then the safety and cost facts. Every clause earns its place and nothing is padded.

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?

For a two-parameter publish tool with no output schema and full annotation coverage, the description supplies the important missing pieces: what gets created (a version) and whether it costs anything. Minor gaps remain around return value or no-op behavior, but these are small relative to the tool's simplicity.

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 site_key (defaults to caller's current draft site) and draft_token (header alternative) are already fully documented in the schema. The description adds no parameter-level detail beyond what the schema provides; 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?

States a specific action (promote staged changes to live) on a specific resource (a site), and names the sibling tools that produce the staged changes (edit_section/set_theme with stage: true). It does not explicitly contrast with publish_site or discard_staged, so the agent must infer the boundary, keeping it just short of a 5.

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?

Clear usage context: call this after staging edits via edit_section or set_theme with stage: true. It also points to restore_version as the recovery path, which tells the agent when to use a different tool. No explicit exclusions (e.g., when to prefer publish_site or discard_staged) are given.

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