Skip to main content
Glama

delete_page

Destructive

Removes a page with version-checked safety; child pages block deletion unless recursive removal is explicitly requested.

Instructions

Delete a page; a page with children is refused unless recursive is true.

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

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
versionYesversion from your last read of the page
recursiveNoAlso delete every page below it; only when the user asked for that

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so safety is partly covered; the description adds the non-obvious behavior that deletion of a page with children is refused unless recursive is set. It does not disclose whether the delete is permanent or to trash, nor how a stale version is handled, which are the remaining behavioral gaps for a destructive tool.

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?

A single sentence with the action first and the refusal condition second; no filler, and trivially front-loaded.

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 three-parameter destructive tool with full schema coverage and a destructive annotation, the definition covers the main hazard an agent must anticipate. Missing only secondary details like permanence of deletion and version-conflict outcomes.

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 every parameter (page, version, recursive) carries its own description, so the baseline is 3. The description only connects recursive to the children-refusal rule and adds nothing about version semantics (optimistic concurrency/conflict) beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Delete a page') plus the key precondition, so an agent can distinguish it from the read_*/write_* siblings at a glance. It does not explicitly name an alternative tool, but the operation itself is unambiguous.

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?

The description supplies a conditional rule ('a page with children is refused unless recursive is true'), which is usage-relevant, but it never says when to delete a page versus another operation or what to do on refusal (e.g., delete children first, or move instead). Guidance is implied rather than explicit.

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