Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_list_users

List WordPress users by role or search term, with pagination and optional email inclusion, to retrieve user data from a WordPress site for management and filtering.

Instructions

List WordPress users with optional role and search filters

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wp_list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
roleNo
searchNo
per_pageNo
include_emailNoInclude email addresses in response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only list operation but does not state pagination defaults, field limitations, whether email addresses are excluded by default, or any authorization requirements. The agent is left without key behavioral context.

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?

The description is a single efficient sentence that front-loads the action and resource. No wasted words, though it misses opportunities to add higher-value parameter or behavior details without becoming long.

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?

For a 5-parameter tool with no annotations and no output schema, the description is too thin. It omits pagination, default response fields, filter semantics, and any return format guidance. An agent would need to guess or make unsafe assumptions to call it confidently.

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 only 20% (only include_email has a description). The description mentions role and search filters but does not clarify role format, search matching criteria, or pagination semantics for page and per_page. It does not compensate sufficiently for the schema gaps.

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?

States a specific verb and resource: 'List WordPress users'. The optional role and search filters further define scope and clearly distinguish it from sibling tools like wp_get_user or wp_create_user. No ambiguity about what this tool does.

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 guidance on when to use this tool versus alternatives such as wp_get_user for a single user, or when to apply specific filters. It does not mention exclusions or prior conditions, leaving the agent to infer usage context.

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