AutoWP MCP Server

update-user

Update an existing WordPress user's profile details including name, email, website, bio, and password. Modify user information through natural language commands.

Instructions

Update an existing WordPress user's profile details

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": {
      "userId": "<userId>"
    },
    "name": "update-user"
  }
}

Input Schema

Name	Required	Description
`bio`	No	New biography/description
`email`	No	New email address
`userId`	Yes	ID of the user to update
`website`	No	New website URL
`lastName`	No	New last name
`password`	No	New password (min 6 characters)
`firstName`	No	New first name
`displayName`	No	New display name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'update' without mentioning whether fields are optionally updated in a patch-like manner, any authorization requirements, or side effects (e.g., email change notification). This lack of detail is a significant gap for a mutation tool.

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 a single, clear sentence with no verbose or redundant content. It front-loads the verb and subject effectively, making it easy to scan.

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?

With 8 parameters and no output schema, the description is minimal but adequate for a straightforward update operation. It does not explain the return value, partial-update semantics, or validation constraints, but the schema covers parameter details. Given the tool's moderate complexity, the description is somewhat incomplete but not critically so.

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%, with each parameter already described (e.g., 'New email address', 'New password (min 6 characters)'). The description adds no additional semantic meaning beyond the schema, so the baseline of 3 is appropriate.

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 'Update an existing WordPress user's profile details' clearly states the verb ('update'), the resource ('existing WordPress user's profile details'), and distinguishes from siblings such as create-user, disable-user, and reset-user-password. It is specific and unambiguous.

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 use this tool versus alternatives like reset-user-password or set-user-role. It implies 'update' for existing users, but does not mention exclusions or preferred scenarios for partial profile vs. specific field updates.

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