wpxmcp

Create a user

create_user

Create a WordPress user with specified role, username, email, and password. Requires administrator access; choose role carefully as administrator grants full site control.

Instructions

Create a WordPress user. Requires an Administrator account. Choose the role deliberately — "administrator" grants full control of the site including plugin and theme installation.

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": {
      "username": "<username>",
      "email": "<email>",
      "password": "<password>"
    },
    "name": "create_user"
  }
}

Input Schema

Name	Required	Description
`url`	No	Website URL.
`meta`	No	Custom fields as key/value pairs, for keys registered with show_in_rest.
`name`	No	Display name.
`email`	Yes	Email address. Must be unique on the site.
`roles`	No	Role slugs, e.g. ["editor"]. Defaults to the site's default role (usually subscriber).
`site_id`	No	Which 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.
`password`	Yes	Initial password. Use a long random value and share it out of band.
`username`	Yes	Login name. Cannot be changed later.
`last_name`	No	Family name.
`first_name`	No	Given name.
`description`	No	Author bio.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.0.0Sep 15, 2026

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 / meta / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

First observedv1.0.0Aug 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds significant behavioral context beyond the annotations: it discloses permission requirements and warns that the 'administrator' role grants full site control including plugin and theme installation. Annotations already establish non-readonly and non-idempotent behavior, so the extra role-security warning is valuable.

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 sentences with no filler. The core purpose is front-loaded, followed immediately by the most important prerequisite and safety warning.

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 create operation with 11 parameters and no output schema, the description covers the key prerequisite and security implications. The remaining parameter details are fully present in the schema, so nothing critical is missing for correct invocation.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful meaning to the roles parameter by explaining the risk of 'administrator' and advising deliberate selection, which is not in the schema's generic role-slug description.

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 'Create a WordPress user' with a specific verb and resource. It clearly differentiates from sibling tools like update_user, delete_user, and list_users.

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 provides a clear prerequisite ('Requires an Administrator account') and vital selection guidance for the roles parameter. It does not explicitly name alternatives or when-not-to-use, but the context is strong enough for an agent to know when to invoke this tool.

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

Deploy Server