Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete page

delete_page
Destructive

Moves a page and all its descendants to the trash while keeping them restorable as unpublished drafts for 30 days; the homepage cannot be deleted.

Instructions

Move a page and all its descendants to the trash. The page leaves the site at once; the group stays restorable with restore_page (as unpublished drafts) for 30 days, after which it is deleted permanently. Cannot delete the homepage.

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

Input Schema

NameRequiredDescriptionDefault
pageIdYesPage id or slug to move to the trash

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

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description nonetheless adds substantive behavior: descendants are removed too, restoration yields unpublished drafts, and permanent deletion follows after 30 days. It does not mention permissions or confirmation requirements.

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?

Three tight sentences, front-loaded with what is destroyed, then recoverability, then the permanent-deletion horizon and the one hard restriction. No redundant restatement of the name or title.

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 single-parameter destructive tool with no output schema, the description covers blast radius, recovery path, timing, and the key exclusion. An agent has everything needed to decide and call correctly.

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 field already documents 'Page id or slug to move to the trash'. The description adds nothing beyond that, so 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?

States a specific verb and resource plus scope: 'Move a page and all its descendants to the trash.' The cascade behavior and the homepage exclusion distinguish it cleanly from siblings like restore_page and unpublish_page.

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?

Explicitly names restore_page as the recovery path and gives the 30-day window during which it applies, plus a hard exclusion ('Cannot delete the homepage'). It stops short of saying when to prefer unpublish_page over deletion, but the recovery guidance is concrete.

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