Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update a user

update_user

Update a WordPress user's profile details, email, password, or roles. Adjusting roles changes access permissions, with administrator granting full site control.

Instructions

Update a user's profile, email, password or roles. Changing roles changes what that person can do — promoting to administrator grants full site control.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe user ID, or "me".
urlNoWebsite URL.
metaNoCustom fields as key/value pairs, for keys registered with show_in_rest.
nameNoDisplay name.
slugNoAuthor archive slug.
emailNoEmail address.
rolesNoReplace the user's roles.
localeNoUser interface locale, e.g. "en_GB".
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.
nicknameNoNickname, used by some themes.
passwordNoNew password. This immediately invalidates the user's existing sessions.
last_nameNoFamily name.
first_nameNoGiven name.
descriptionNoLonger descriptive text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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
    • changedInput schema / properties / id / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "const": "me",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "const": "me",
+    "type": "string"
+  }
+]
    • addedInput schema / properties / meta / propertyNames
      Added value: +{
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already provide state-change and idempotency hints, and the description adds a meaningful consequence: changing roles alters permissions, with administrator promotion granting full site control. This goes beyond the structured hints, though it does not cover all side effects such as required privileges.

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?

Two sentences with no filler; the core action is front-loaded and the risk warning is placed at the end. Every clause contributes useful information.

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?

For a 14-parameter mutation tool with no output schema, the description is adequate but incomplete. It does not state partial-update semantics, what the return value is, or what privileges are required. The schema covers parameter meaning, but tool-level behavioral context is missing.

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. The description adds semantic weight to the roles parameter by explaining that changing roles changes what the person can do, which goes beyond the schema's "Replace the user's roles." Other parameters are fully explained by the schema.

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 "Update a user's profile, email, password or roles," giving a specific verb, resource, and scope. It clearly distinguishes updating from sibling tools like create_user, delete_user, and get_user 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 Guidelines2/5

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

The description provides no guidance on when to choose this tool over alternatives, nor does it state prerequisites or exclusions. It communicates what the tool does but not the context in which it should be invoked.

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