Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: List plugins

wordpress_list_plugins
Read-only

List installed WordPress plugins by status, including version and details, to audit active or inactive plugins on a site.

Instructions

[UNIFIED] List installed WordPress plugins. Shows plugin status (active/inactive), version, and details.

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": {
      "site": "<site>"
    },
    "name": "wordpress_list_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
statusNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe read, so the description's job is to add context. It does add that results include active/inactive status, version and details, but says nothing about authentication requirements, result volume, or pagination behavior for sites with many plugins.

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 short sentences, front-loaded with the action and scope, with no filler. The only wasted token is the unexplained "[UNIFIED]" tag, which conveys nothing to the agent.

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?

For a simple two-parameter read tool with a readOnly annotation and no output schema, the description covers the essentials of what is returned. It falls short on the filter parameter's contract and on result-set behavior, which matter even for a lightweight list operation.

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 both parameters are undocumented in structured data. The description never mentions the optional `status` parameter or what values it accepts (presumably active/inactive/all), and gives no hint about what `site` requires (slug, ID, or URL) — it only mentions status as a returned field, not a filter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List installed WordPress plugins" gives a specific verb and resource, and the second sentence names the fields surfaced (status, version, details). It is clear what the tool does, though the unexplained "[UNIFIED]" prefix adds no meaning and there is no explicit differentiation from the plugin-related siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus alternatives, no prerequisites (e.g. site permissions), and no exclusions. The agent must infer usage entirely from the tool name, and the existence of a similarly-named plugin-listing sibling makes that inference risky.

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

Deploy Server

Other Tools