Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Restore page

restore_page
Destructive

Recover a deleted page group from trash, returning it and all descendants as unpublished drafts with content, history, and IDs; if the original parent is gone, the root returns at top level.

Instructions

Restore a deleted page group from the trash: the page and every descendant deleted with it come back, all as unpublished drafts, with their content, history and ids. When the original parent no longer exists the page comes back at the top level. Refused with CONFLICT, restoring nothing, when a live page already uses one of the group's slugs (the error names the slug) or one of the pages is still live; refused with PLAN_LIMIT_EXCEEDED when the restored pages would exceed the organization's page limit. Needs pages:delete. Returns the restored root page with its published state.

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": {
      "trashId": "<trashId>"
    },
    "name": "restore_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
trashIdYesTrash id of the group to restore, as list_trashed_pages shows it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=true; the description goes far beyond by disclosing that descendants come back as unpublished drafts with content, history and ids preserved, that an orphaned page is reparented to top level, that CONFLICT restores nothing and names the offending slug, that PLAN_LIMIT_EXCEEDED is possible, and that the required permission is pages:delete. This is exactly the behavioral detail annotations cannot carry.

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?

The description is front-loaded with the core action and outcome, then layers edge cases and error conditions in short declarative clauses. Every sentence carries distinct information — restoration scope, draft state, orphan handling, two error modes, permission, return value — with no filler.

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?

For a one-parameter mutation with no output schema, the description covers the mutation's blast radius, identity preservation, error semantics, permission requirement, and return value ('the restored root page with its published state'). Nothing an agent needs in order to call it correctly or interpret failures 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 description coverage is 100% and there is a single parameter whose schema description already explains it is the trash id as shown by list_trashed_pages. The description adds no further syntax or format guidance for trashId, so the baseline 3 applies.

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 opens with a specific verb and resource ('Restore a deleted page group from the trash') and immediately scopes it to 'the page and every descendant deleted with it', which distinguishes it from sibling restore_media and from publish/unpublish tools. An agent can identify the operation without opening the schema.

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?

Usage context is clear: this is the tool for bringing back a trashed page group, with explicit preconditions (must not collide with a live slug, must fit the org page limit) and the required permission pages:delete. It does not explicitly name an alternative tool, but the preconditions effectively define when the call will fail, which is the practically useful guidance here.

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