Skip to main content
Glama

mcp_delete_user

Deletes a WordPress user by site and ID and optionally reassigns their posts and links; without reassignment, those posts and links are also deleted.

Instructions

Delete a user. WITHOUT reassign, all of the user's posts and links are deleted too. The current API user cannot delete itself.

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

Input Schema

NameRequiredDescriptionDefault
idYesUser ID to delete
siteYesSite id (see list_sites)
reassignNoUser ID to reassign the deleted user's posts and links to (strongly recommended)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.14.0
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / reassign / description
      Previous value: -"User ID to reassign content to"New value: +"User ID to reassign the deleted user's posts and links to (strongly recommended)"
    • changedInput schema / properties / reassign / type
      Previous value: -"number"New value: +"integer"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id"
      -]New value: +[
      +  "site",
      +  "id"
      +]
  3. First observedv2.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two genuinely important behaviors: the cascading deletion of posts and links when reassign is omitted, and the self-deletion prohibition for the current API user. It omits irreversibility, permission requirements, and error conditions, so it is helpful but incomplete for a destructive operation.

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, each carrying distinct information, with the destructive default stated up front. No filler and no redundancy.

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 three-parameter tool with no annotations and no output schema, the description covers the essential risks: cascade deletion and the self-delete restriction. Missing are permission prerequisites and whether deletion is reversible, which would round it out.

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 earns above baseline by explaining the actual consequence of omitting 'reassign' rather than merely restating the schema's 'strongly recommended' note. That converts a soft hint into a concrete data-loss warning the agent can act on.

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?

States a specific verb and resource ('Delete a user') immediately, and the following sentences scope the operation precisely. It does not, however, differentiate itself from the sibling 'wp_delete_user', which by name appears to perform the same job, leaving the agent to guess which to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives conditional guidance on how to invoke it safely ('WITHOUT reassign, all of the user's posts and links are deleted too'), which implies when to supply reassign. It stops short of saying when to use this tool rather than the sibling delete-user tool, or what prerequisite authority is needed.

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