Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: List users

wordpress_list_users
Read-only

Retrieve paginated WordPress users with names, usernames, emails, and roles, filtered by site and optional role, to support user audits and administration.

Instructions

[UNIFIED] List WordPress users. Returns paginated list of users with name, username, email, and roles.

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": {
      "site": "<site>"
    },
    "name": "wordpress_list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
siteYes
rolesNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description adds useful context that the result is paginated and which fields come back. It does not disclose the default page size, the authorization/capability needed to enumerate users (a potentially sensitive operation), or what an empty result looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the verb and resource front-loaded and the return contents immediately after. The bracketed "[UNIFIED]" tag is dead weight but the rest earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and zero parameter coverage, the description should carry more of the burden. It never explains the required 'site' target, the roles filter syntax, or pagination defaults — the main things an agent must get right to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters. The description only implies pagination, leaving 'site' (the sole required param), 'roles' filtering, and the per_page default of 10 entirely undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List WordPress users") and names the fields returned. It does not distinguish itself from the sibling wordpress_specialist_wp_user_list, and the "[UNIFIED]" prefix carries no meaning for an agent.

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?

No when-to-use guidance, no exclusions, and no mention of alternatives such as the specialist user-list variant. The required 'site' parameter also goes unexplained, so an agent gets no help on prerequisites before calling.

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