wpxmcp

Get a user

get_user

Read-only

Fetch a WordPress user by ID, or use "me" for the authenticated account, to return their roles and notable capabilities.

Instructions

Fetch one user by ID, or the authenticated user with id: "me". Includes roles and a summary of notable capabilities when permitted.

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": "get_user"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The user ID, or "me" for the account this server authenticates as.
`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.

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
```

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"
+  }
+]

First observedv1.0.0Aug 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds useful behavioral context by disclosing that the response includes roles and a summary of notable capabilities, and that this is conditional on permissions ('when permitted').

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?

One tight sentence with no filler. The core operation is front-loaded, the special-case id is mentioned immediately, and the return-relevant detail about roles/capabilities earns its place.

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 straightforward read operation, the description covers the essential return content and special id behavior. There is no output schema, but the description names key response components. Minor gaps remain around exact conditions for 'permitted' capabilities and error behavior, but these are not critical for call selection.

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%, so the schema already documents both 'id' and 'site_id' thoroughly. The description reinforces the 'me' special value but adds little parameter meaning beyond what the schema provides.

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?

Uses a specific verb ('Fetch') and resource ('one user'), and clearly distinguishes the single-user lookup from list_users. The special id 'me' is explicitly documented, adding precision about the operation's scope.

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?

States the two clear use cases: fetch by ID or fetch the authenticated user via 'me'. It implies this is for individual user retrieval rather than listing all users, though it does not explicitly name list_users as the alternative.

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

Deploy Server