Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a user

delete_user
Destructive

Permanently remove a WordPress user account. Requires explicit confirmation and reassignment of their content to another user to prevent data loss.

Instructions

Delete a user. WordPress has no trash for users, so this is permanent and requires confirm: true. You must say what happens to their content: reassign it to another user (strongly preferred) or let it be deleted with them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe user ID to delete.
confirmNoRequired — user deletion cannot be undone.
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
reassign_toNoUser ID to inherit this user's posts. Omit only if you truly want their content deleted too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / id / minimum
      Added value: +1
    • addedInput schema / properties / reassign_to / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / reassign_to / minimum
      Added value: +1
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark destructiveHint: true, but the description adds meaningful context beyond that: deletion is permanent because there is no trash, confirm must be true, and content must be either reassigned or deleted. This gives the agent important behavioral expectations beyond the structured annotations.

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?

The description is two concise sentences with no filler, and the most important information—permanence and mandatory confirm—is front-loaded. Every sentence contributes directly to correct invocation.

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 4-parameter tool with no output schema, the description covers the critical behavioral context: permanence, confirmation requirement, and content disposition. It could additionally note that id is required, but the schema already covers that, so nothing essential is missing.

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 description coverage is 100%, so every parameter is already documented structurally. The description reinforces the semantics of confirm and reassign_to, but does not add new parameter-level information beyond what the schema provides.

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 states the specific action and resource: 'Delete a user', and immediately clarifies the key semantic that WordPress has no trash for users, so deletion is permanent. This clearly distinguishes it from sibling tools like update_user or 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?

It gives explicit conditions for use: deletion requires confirm: true and the agent must decide what happens to the user's content, with reassignment strongly preferred. It doesn't explicitly name alternatives or say when not to use it, but the required workflow is clearly specified.

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