Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Revert to published

revert_to_published
Destructive

Discard all draft changes and revert a page to its last published version using its page ID or slug.

Instructions

Discard all draft changes and revert a page to its last published version.

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": "revert_to_published"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesPage id or slug to revert

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 revert"New value: +"Page id or slug to revert"
    • addedInput schema / required
      Added value: +[
      +  "pageId"
      +]
  2. First observedv0.73.1

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description earns credit for specifying exactly what is destroyed ('all draft changes'), which is the key consequence an agent needs before calling a destructive tool. It stops short of mentioning recoverability, permissions, or the resulting state of the page.

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?

One short sentence, front-loaded with the destructive consequence and followed by the outcome. Every clause carries information and there is no filler.

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 single-parameter, no-output-schema tool with annotations covering the destructive profile, this is nearly complete. The only modest gap is that it doesn't state what the call returns or whether the reverted page remains accessible, which is minor given the 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?

There is a single parameter with 100% schema description coverage ('Page id or slug to revert'), so the schema already does the work. The description adds no additional meaning about accepted identifiers or format, making this a baseline case.

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?

The description gives a specific verb ('revert') plus the resource ('a page'), and qualifies it with the exact scope ('to its last published version' while discarding draft changes). This is clearly distinct from neighboring page tools such as delete_page or create_page.

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?

Usage is only implied: an agent can infer this is for undoing unpublished draft work, but the description never says when to prefer this over deleting a page, editing drafts directly, or any other recovery route. There are no stated prerequisites or exclusions.

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