Skip to main content
Glama

Set wiki page deprecated

set_wiki_page_deprecated
Destructive

Mark a wiki page DEPRECATED — kept for reference, no longer current — or take the mark off (deprecated: false), as the page's own screen does. Optionally say why ('reason', at most 500 characters) and which page to read instead ('replacementPageId', a page you can open). Marking a page that is already marked changes its reason and replacement. The mark is the page's label 'deprecated' (so search_wiki with label 'deprecated', and CQL label = deprecated, list such pages); who marked it, when and why is kept in the page's history, and the page, its tree row and search show it. It is no edit of the text and makes no version; an approval of the page stands. Requires permission to edit the page.

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": {
      "id": "<id>"
    },
    "name": "set_wiki_page_deprecated"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPage id.
reasonNoWhy it is no longer current, in a sentence. Ignored when taking the mark off.
deprecatedNotrue to mark the page deprecated (or change its reason and replacement), false to take the mark off.
replacementPageIdNoThe page to read instead (its id, as search_wiki gives it). Ignored when taking the mark off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=true) by disclosing consequences: the 'deprecated' label appears in search_wiki and CQL queries, who/when/why is recorded in page history, the mark surfaces on the page, tree row and search, no version is created, existing approvals stand, and edit permission is required. This is exactly the operational context an agent needs for a state-mutating call.

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?

Single dense paragraph that front-loads the two modes of operation before moving to side effects and permissions. Nearly every clause carries information; minor length creep from enumerating surfaces ('the page, its tree row and search').

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 4-parameter mutation tool with no output schema, the description covers mode semantics, side effects, searchability, history, permission requirements, and idempotent re-marking. Nothing an agent would need to invoke it correctly 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%, so the baseline is 3, but the description adds meaning the schema lacks: the 500-character limit on 'reason', the fact that replacementPageId must be a page the caller can open, and that both optional params are ignored when unmarking.

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 (mark a wiki page DEPRECATED / take the mark off) and defines the semantic meaning ('kept for reference, no longer current'). It also distinguishes the operation from text editing ('It is no edit of the text and makes no version'), so it is separable from update_wiki_page without opening either 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?

Gives clear operating context: use deprecated:false to unmark, marking an already-marked page updates reason/replacement, and the operation mirrors 'the page's own screen'. It implicitly rules out text edits but never names update_wiki_page directly or states exclusions for bulk/multi-page use.

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