Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Publish page

publish_page
Destructive

Publish a page or re-publish its latest draft changes, including both content and layout, so updates go live.

Instructions

Publish a page (or re-publish with the latest draft changes). Publishes both content and layout.

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": {
      "pageId": "<pageId>"
    },
    "name": "publish_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesPage id or slug to publish

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / pageId / description
      Previous value: -"Page id to publish"New value: +"Page id or slug to publish"
    • addedInput schema / required
      Added value: +[
      +  "pageId"
      +]
  2. First observedv0.73.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation and risk profile are known. The description adds genuine context that both content and layout are pushed, but it does not explain what is destroyed or overwritten on the live page, or whether the prior published version is recoverable — meaningful gaps for a destructive operation.

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 short sentences, front-loaded with the action and immediately followed by the scope qualifier. Nothing is redundant, though the parenthetical sits mid-sentence rather than being structured as a separate usage note.

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

Completeness3/5

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

For a one-parameter tool with annotations covering safety and no output schema, the description is close to adequate. It nonetheless leaves open whether publishing requires holding the page lock (a sibling exists for taking over locks) and whether the action is reversible, which matter for a destructive publish.

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% and the single pageId parameter is documented as "Page id or slug to publish." The description adds no further meaning about that parameter, so the schema does all the work; this is the baseline case.

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 states a specific verb and resource ("Publish a page") and adds scope ("Publishes both content and layout"), which lets an agent distinguish it from unpublish_page and update_page_* siblings. It does not explicitly name the inverse operation, so differentiation comes from the verb alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical "or re-publish with the latest draft changes" implies the trigger condition: draft edits are pending and need to go live. However, no alternative is named (e.g., unpublish_page, update_page_layout) and no preconditions such as page lock ownership are mentioned, so guidance is implied rather than explicit.

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

Deploy Server

Other Tools