Skip to main content
Glama
ni-c

wikijs-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete a user

delete_user
DestructiveIdempotent

Remove a user account from Wiki.js. Provide a replacement user to inherit their pages; a confirmation token is required to complete deletion.

Instructions

Removes an account. Wiki.js needs somebody to inherit the pages it authored, so replace_with_user_id is required — pass the id of the account that should own them afterwards. Requires a confirmation token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesNumeric Wiki.js id.
confirm_tokenNoToken from this tool’s previous, unconfirmed call. Omit it to receive one.
replace_with_user_idYesAccount that inherits the deleted user’s pages.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
truncatedNoPresent only when the answer was shortened to fit the budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / replace_with_user_id / maximum
      Previous value: -9007199254740991New value: +2147483647
    • changedInput schema / properties / user_id / maximum
      Previous value: -9007199254740991New value: +2147483647
  2. Changed2 schema fields changedv0.2.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "properties": {
+    "truncated": {
+      "additionalProperties": true,
+      "description": "Present only when the answer was shortened to fit the budget.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  3. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag this as destructive and non-read-only. The description adds the meaningful consequence that the deleted user's authored pages must be transferred to another account, and that confirmation is part of the flow. It does not spell out irreversibility, but destructiveHint covers the core safety signal.

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 short sentences deliver the action, the critical ownership-transfer constraint, and the confirmation requirement with no filler. The most important behavioral information is 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?

Between the description, full parameter schema, output schema, and annotations, an agent has almost everything needed to invoke deletion correctly. The only minor gap is that the two-step confirmation flow (omit confirm_token first, receive token, then confirm) is left to the schema rather than stated explicitly.

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?

With 100% schema description coverage, every parameter is already documented. The description restates the replace_with_user_id requirement and the confirmation-token need without adding much parameter-level detail beyond the schema, so it meets the baseline but does not elevate it.

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?

The description opens with 'Removes an account,' a specific verb-object pair that clearly identifies this as a permanent user-deletion tool. The added detail about page inheritance distinguishes it from non-destructive user-state tools like set_user_active without ambiguity.

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 states the key precondition ('replace_with_user_id is required') and the confirmation-token requirement, giving an agent clear context for when deletion can proceed. It does not explicitly call out when to prefer set_user_active over delete_user, so it stops short of full alternatives guidance.

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