Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List trashed pages

list_trashed_pages
Read-only

Lists deleted page groups in trash, newest first, showing restore IDs, deletion details, descendant counts, and permanent-deletion expiry so you can review and restore pages.

Instructions

List the page trash, newest first. Each entry is one deleted group - a page plus the descendants deleted with it: id (the trash id restore_page takes), name, slug, deletedAt, deletedById and deletedByName, descendantCount, and expiresAt, when the group is deleted permanently (30 days after deletion). Only groups the caller holds pages:delete on are listed; without it the list is empty.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real value on top: newest-first ordering, one entry per deleted group, and the 30-day permanent-deletion expiry. It omits whether the list is paginated or capped, so an agent cannot tell if a large trash is fully returned.

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 sentences, front-loaded with the operation and ordering, then the entry shape, then the permission caveat. The field enumeration is dense but justified because no output schema exists.

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?

With no output schema, the description carries the return-value burden and does so fully, including field meanings, ordering, expiry window, and the empty-list behavior without pages:delete. Only pagination behavior is unaddressed, a minor gap for a zero-param list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline applies. The description spends its space on return-field semantics (id, descendantCount, expiresAt) rather than params, which is the right allocation given the empty schema.

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?

Specific verb and resource ("List the page trash") plus ordering ("newest first") and scoping to deleted items, which distinguishes it from list_pages without naming a 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?

Implies use when you need deleted pages and explicitly ties the returned id to restore_page ("the trash id restore_page takes"), routing the caller to the follow-up tool. It states the permission gate (pages:delete) but never explicitly contrasts with list_pages or says when trash listing is inappropriate.

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