Skip to main content
Glama

Remove page

wiki_remove
Destructive

Remove a page. Requires the wiki's remove capability. Set recursive only when the user requested deletion of the entire subtree. Read the page and use its revision; a wiki change guard also protects against intervening authored changes. The result's brokenLinks name the pages and records whose links pointed at what was removed.

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": {
      "path": "<path>",
      "org": "<org>"
    },
    "name": "wiki_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe wiki's name, a colon, then the page's dot-separated path (general:docs.deploy).
messageNoA brief note on the change describing the deletion.
ifChangeNoThe latest wiki change ID from wiki_changes at the wiki root.
recursiveNoAlso delete all descendant pages.
ifRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the fundamental risk is known; the description adds non-obvious behavior on top: a wiki change guard against intervening authored changes, the revision-based precondition, the capability requirement, and the broken-link side effects of removal. It could go further on irreversibility or confirmation expectations, which is why it is not a 5.

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?

Four tight sentences, front-loaded with the action, then preconditions, then the return-value note. No filler, though the return-value sentence could be folded in more economically.

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 destructive mutation with no output schema, the description covers the essential ground: capability requirement, revision guard, recursive scoping, and what the result's brokenLinks contain. Missing are the failure mode for a nonexistent path and any differentiation from the other deletion tools listed alongside it.

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?

With 83% schema description coverage the baseline is 3, but the description adds genuine meaning beyond the schema: `recursive` is scoped to whole-subtree requests and `ifRevision` is tied to a read-then-delete workflow. `ifChange` and `message` are not elaborated in the description, leaving a small gap.

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?

"Remove a page" is a specific verb+resource pair that tells an agent exactly what the tool acts on, and the mention of "the pages and records whose links pointed at what was removed" clarifies that page removal has graph-wide link side effects. It does not differentiate itself from the similarly named sibling deletion tools, so it falls short of a 5.

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?

The description gives real selection guidance: the caller must first read the page and pass its revision, and `recursive` should only be set "when the user requested deletion of the entire subtree." It also states a precondition (the wiki's remove capability) that gates use. It stops short of 5 because it never states when this tool should be avoided in favor of another deletion path.

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