mcp-wordpress

wp_users_update

Partially update a WordPress user by ID: change profile fields, password, or roles. Self-update allowed; modifying other users requires elevated capabilities.

Instructions

Partially update a user by id. Can change profile fields, password, or roles. Self-update permitted; updating other users requires elevated capabilities.

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

Input Schema

Name	Required	Description	Default
`id`	Yes
`url`	No
`name`	No
`slug`	No
`email`	No
`roles`	No
`locale`	No
`nickname`	No
`password`	No
`last_name`	No
`first_name`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses that updates are partial (only provided fields change) and mentions permission boundaries. This adds valuable behavioral context beyond the tool name, though it does not detail return values or side effects like password hashing, leaving some gaps.

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 sentences, front-loaded with the core purpose and immediately followed by key permissions. Every word earns its place; there is no filler or repetition.

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?

The description covers the essential aspects: purpose, partial update behavior, and authorization. It does not explain return values or error conditions, but given the simple update nature and the absence of an output schema, it is reasonably complete for an agent to use the tool correctly.

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 0%, so the description must compensate. It groups parameters into 'profile fields, password, or roles,' which gives high-level meaning, but it does not explain individual parameters beyond their schema types. The schema property names are self-explanatory for most fields, but the description adds minimal semantic detail about how roles or password updates behave.

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 clearly states the tool's function: 'Partially update a user by id.' It specifies the resource (user), the action (update), and the identifier (id). It also distinguishes from sibling tools by noting it can change profile fields, password, or roles, which aligns with its update role versus create/delete/list tools.

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?

The description gives clear context: this is for updating an existing user by id, and it notes authorization requirements ('Self-update permitted; updating other users requires elevated capabilities'). While it doesn't explicitly state when not to use it, the 'partial update' wording and resource-specific nature make usage clear without needing exclusions.

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

Deploy Server