Skip to main content
Glama

Move a published page to Trash

delete_page

Move one of your published pages to Trash. This takes the page OFFLINE immediately — its private link stops working right away. It is RECOVERABLE, not a permanent delete: the page sits in the owner's miinideck dashboard Trash and can be brought back with restore_page (until it is later permanently purged from Trash). Because this unpublishes a link the user may have already shared, CONFIRM with the user before calling — name the page you're about to delete and wait for a clear yes. Identify the page with page (its viewer URL or slug, e.g. from list_pages). You can only delete your own pages.

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": {
      "page": "<page>"
    },
    "name": "delete_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesThe page's viewer URL or its slug (the part after the last '/').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: it discloses immediate unpublication ('its private link stops working right away'), reversibility semantics (Trash + restore_page, with the caveat of later permanent purge), and the required user-confirmation flow. These are exactly the side-effect details an agent needs before invoking a destructive-looking 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?

Front-loaded with the action and the offline/recoverable distinction, then the confirmation ritual, then parameter guidance — a sensible priority order. It runs slightly long, with the Trash/purge caveat parenthetical restating the recoverability point, but no sentence is genuinely wasted.

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 tool with no output schema and no annotations, the description supplies scope, side effects, reversibility, safety protocol, and identifier source. Nothing an agent needs in order to call it correctly and safely is missing.

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?

Schema coverage is 100% and already documents the `page` parameter as viewer URL or slug, so the baseline is 3. The description adds marginal value by giving an example ('e.g. from list_pages'), pointing the agent at the sibling tool that produces valid identifiers.

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 ('Move one of your published pages to Trash') and immediately scopes it against the scarier sibling operation by declaring it recoverable rather than a permanent delete. An agent can distinguish this from restore_page, update_page, and get_page from the description alone.

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

Usage Guidelines5/5

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

Gives an explicit precondition ('CONFIRM with the user before calling — name the page you're about to delete and wait for a clear yes'), an ownership restriction ('You can only delete your own pages'), and names the recovery alternative restore_page. This is close to a complete decision procedure.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources