elementor-mcp-agent

wp_plugin_update

Destructive

Update one or more WordPress plugins to the latest version with wp-cli. Requires a confirmation token for safety.

Instructions

Update one or more plugins on a site to their latest version. Requires confirmation token (uses wp-cli).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plugins": "<plugins>"
    },
    "name": "wp_plugin_update"
  }
}

Input Schema

Name	Required	Description
`site_id`	No
`plugins`	Yes	Plugin slugs to update, e.g. ['elementor', 'elementor-pro']. Use 'all' for everything outdated.
`confirmation`	No

Output Schema

Name	Required	Description	Default
`mode`	Yes
`plugins`	Yes
`command`	No
`stdout`	No
`stderr`	No
`exit_code`	No
`confirmation_token`	No
`expires_in_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already indicate destructive behavior (destructiveHint=true), and the description adds the need for a confirmation token and that it uses wp-cli, providing useful behavioral context beyond annotations. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that efficiently conveys the action and key requirement. No redundant information.

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?

The description covers the basic purpose and a critical requirement (confirmation), but it does not clarify the role of site_id (optional or required) or the return value format, despite having an output schema. It is adequate but leaves gaps for an agent to fully understand configuration and outcomes.

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 33%, and the description does not explain the site_id or confirmation parameters. It only mentions confirmation token generically, without linking to the schema parameter. The schema provides some help for the 'plugins' parameter but overall the description adds minimal semantic value.

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?

The description clearly states the tool updates one or more plugins to their latest version, using a specific verb and resource. It distinguishes from sibling tools like wp_plugin_list (list) and wp_cli_run (general command).

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?

The description mentions a requirement for a confirmation token, which provides some usage context, but it does not explicitly state when to use this tool versus alternatives or when not to use it. Guidance on required parameters is minimal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.