wp_get_users tool reference for StifLi Flex MCP
Read-onlylists users with basic fields: ID, login, display name, and roles. It can optionally include registration date, avatar, post count, and pagination.
Description
lists users with basic fields: ID, login, display name, and roles. It can optionally include registration date, avatar, post count, and pagination.
What it is for
- Viewing users and roles.
- Auditing authors or site accounts.
Example use case
author audit.
Sample prompt
List all editor and author accounts with their display names and post counts.
Sample response
{
"tool": "wp_get_users",
"status": "ok",
"items": []
}
What does wp_get_users do?
lists users with basic fields: ID, login, display name, and roles. It can optionally include registration date, avatar, post count, and pagination.
Does wp_get_users modify site data?
No. It is a read-only operation and does not modify content or settings.
Which capability is commonly required?
It usually runs under controls compatible with list_users and the active MCP profile.
How should wp_get_users be used safely?
Limit scope with filters and pagination to reduce overexposure of data.