Skip to main content
Glama

wp_delete_user

Delete a WordPress user permanently and reassign authored content to another user; dry-run preview prevents accidental deletion and production writes require explicit approval.

Instructions

PERMANENTLY delete a user; their content goes to reassign (0 = deleted too).

There is no trash and no undo for a user: WordPress's REST API only deletes with force, so this cannot be reversed from here. reassign decides what happens to everything they authored - posts, pages, media: the DEFAULT of 0 DELETES THEIR CONTENT WITH THEM, while any other user id transfers authorship to that user (get one from wp_list_users). If the account wrote anything you want to keep, pass a reassign target. DEFAULTS TO dry_run=true (returns a preview that spells out which of the two outcomes you are about to get; deletes nothing). Pass dry_run=false to delete. Requires the REST transport and an administrator app password. Prod writes require allow_prod=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNo
installYes
user_idYes
reassignNo
allow_prodNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.4.0

TDQS

A4.2/5.0
Behavior5/5

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

No annotations are present, so the description carries full responsibility. It thoroughly discloses permanence, force-delete behavior, no undo, content deletion risk, reassign semantics, dry-run behavior, and production safeguards.

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?

The description is focused and well-structured, with important safety warnings. Minor redundancy exists around permanence and deletion guarantees, but each statement contributes useful context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers side effects, safety defaults, and reassign behavior thoroughly. However, the required install parameter is not addressed, and the return value for a successful delete is not described, leaving the description incomplete for a 5-parameter tool with no output schema.

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?

The schema has zero descriptions, and the description compensates well for reassign, dry_run, allow_prod, and user_id implicitly. However, the required 'install' parameter is never explained, leaving a meaningful gap in parameter understanding.

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?

Clearly states the tool permanently deletes a user and how content is handled via reassign. The verb-resource relationship is explicit and distinguishes it from user-related sibling tools like wp_update_user and wp_create_user.

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?

Provides clear operational guidance: dry_run defaults to true, pass false to delete, use allow_prod for production, and reassign to preserve authored content. Does not explicitly contrast with sibling tools, but the conditions and prerequisites are clearly stated.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ad02/wp-ops-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server