wordpress_create_roleCreate custom user roles for WordPress by defining a role slug and display name. Grant specific permissions to control user capabilities.
Create a custom user role
| Name | Required | Description | Default |
|---|---|---|---|
| role | Yes | ||
| displayName | Yes |
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state what happens if the role already exists, what capabilities the new role has initially, or any permission requirements. This is a mutation operation with significant unspecified behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficiently worded sentence. It contains no superfluous text and is front-loaded with the key purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool is a mutation with no annotations, no output schema, and 0% schema documentation coverage, the description is too sparse. It provides the basic purpose but omits critical context like conflict behavior, initial capabilities, and response format, leaving the agent uncertain about invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for parameter meaning. 'role' and 'displayName' are self-explanatory to a degree, but the description adds no clarification on formats, uniqueness constraints, or how these parameters relate to WordPress role registration.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Create') and the target resource ('a custom user role'), which is specific and easily distinguished from sibling tools like get_roles, delete_role, and assign_role.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description does not mention scenarios where creating a role is appropriate or how it relates to capability management.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.