kinsta_plugins_updateUpdate a WordPress plugin to a specific version on a Kinsta environment. Provide environment ID, plugin slug, and target version to trigger the update and receive an operation ID.
Update a single plugin to the latest version. Returns an operation_id.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The plugin name/slug to update | |
| env_id | Yes | The environment ID | |
| update_version | Yes | The plugin version to install |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the operation_id return value, which is useful, and the openWorldHint annotation already signals external side effects. However, it does not explain that the update is likely asynchronous, how to track the operation_id, or other consequences beyond updating a plugin.
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?
Two short sentences, front-loaded with the action and scope, with no filler. The return value is included 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?
For a side-effectful update with three required params and no output schema, this is adequate but thin: an agent gets all required params from the schema and knows the return type, but is not told to check the operation status or that the update is asynchronous. The 'latest' vs. update_version ambiguity also leaves an incomplete mental model.
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 100%, so a baseline of 3 would normally apply. The description's phrase 'latest version' contradicts the schema's update_version definition ('The plugin version to install'), so it provides misleading rather than additive parameter meaning.
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 names the verb ('Update') and resource ('a single plugin'), and 'single' distinguishes it from the bulk-update sibling. The 'latest version' wording is slightly at odds with the schema's required update_version, which prevents a perfect 5.
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?
'Single plugin' gives a clear scope and implicitly tells an agent not to use this for multiple plugins, with kinsta_plugins_bulk-update as the obvious alternative. It does not explicitly name the bulk tool or state a when-not-to-use condition, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.