Skip to main content
Glama
cvrt-jh

wordpress-mcp

by cvrt-jh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mcp_list_roles

List all available WordPress user roles for a specified site. Use it to audit permissions and determine which roles can be assigned to users.

Instructions

List all available WordPress user roles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / site
      Added value: +{
+  "description": "Site id (see list_sites)",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "site"
+]
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'List' strongly implies a harmless read-only enumeration, which is adequate context for a trivial lookup, but the description does not state read-only semantics, permission requirements, or whether role slugs/capabilities are returned.

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?

A single front-loaded sentence with no waste. It is appropriately sized for a simple list operation, though it is arguably so terse that it omits useful context.

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

Completeness3/5

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

For a one-parameter read-only tool with no output schema, the description is minimally viable. It does not describe the shape of returned roles (name vs. slug vs. capabilities) or that the 'site' id comes from list_sites, leaving minor gaps an agent would otherwise guess at.

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 coverage is 100% with the single 'site' parameter fully documented in the schema. The description adds no parameter detail, so the schema does all the work; baseline 3 applies.

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 (list) and resource (WordPress user roles) with a clear scope of 'all available'. An agent can distinguish it from siblings like mcp_list_users or mcp_change_user_role, though the description does not explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the name and description: call this to enumerate roles before assigning one. There is no explicit when-to-use guidance, no mention of prerequisites, and no reference to related tools like mcp_change_user_role that would consume the returned roles.

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