elementor-mcp-agent

wp_plugin_list

Read-onlyIdempotent

List installed WordPress plugins with version, status, and available updates using WP-CLI. Filter to show only outdated plugins.

Instructions

List installed plugins on a site with name, version, status (active/inactive), and update_version (if outdated). Uses WP-CLI for accurate version data including update_version.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wp_plugin_list"
  }
}

Input Schema

Name	Required	Description	Default
`site_id`	No
`only_outdated`	No

Output Schema

Name	Required	Description	Default
`total`	Yes
`plugins`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 27, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, indicating safe repeated reads. The description adds useful context by specifying data source (WP-CLI) and that update_version is provided if outdated. No contradictions.

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?

Two sentences, front-loaded with the main purpose. No filler words. Could benefit from explicitly listing parameters for better structure, but overall concise.

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?

Given the simple tool, annotations, and existence of an output schema, the description covers the main purpose and data fields. It lacks explicit parameter descriptions and does not explain the return format beyond field names, but the output schema likely compensates.

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 0%, so the description must compensate. It vaguely implies site_id by 'on a site' and mentions 'update_version (if outdated)' hinting at filtering, but does not explicitly describe the 'only_outdated' parameter or explain the parameters' meaning beyond their names.

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 lists installed plugins with specific fields (name, version, status, update_version). It uses a specific verb and resource, distinguishing it from sibling tools like wp_plugin_update or wp_cli_run.

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 using WP-CLI for accurate version data, hinting at why to use this tool, but it does not explicitly state when to use it over alternatives or when not to use it. No exclusions or alternatives are named.

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