kinsta_plugins_list-wpList WordPress plugins for an environment, including details from the WordPress.org repository. Filter by status or check for vulnerabilities and available updates.
List WordPress plugins with details from the WordPress.org repository for an environment.
| Name | Required | Description | Default |
|---|---|---|---|
| column | No | ||
| env_id | Yes | The environment ID | |
| status | No |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey readOnly, openWorld, and idempotent behavior. The description adds useful context that the data comes from the WordPress.org repository rather than only local environment state, but it does not disclose output shape, pagination, or external dependency behavior. No contradiction with annotations.
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?
A single, front-loaded sentence with no filler. It communicates the core action, resource, source, and scope efficiently.
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?
With three parameters, no output schema, and no guidance about optional filter semantics, the description is underspecified. An agent may call it correctly for a simple list, but it will struggle to know when to use column/status or how results are structured. It also does not differentiate this tool from kinsta_plugins_list.
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 coverage is only 33%: env_id is described, but column and status are enum-only with no descriptions. The description does not explain what 'column' controls or how status filtering works, so the description fails to compensate for the low schema coverage.
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 states a specific verb ('List'), resource ('WordPress plugins'), and scope ('for an environment'). It also names the data source ('WordPress.org repository'), which helps distinguish it from the sibling kinsta_plugins_list.
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 given on when to use this tool versus kinsta_plugins_list, kinsta_plugins_update, or other plugin-related siblings. The environment scope is implied, but there are no exclusions, alternatives, or scenario-based instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.