Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp plugin list

wordpress_specialist_wp_plugin_list
Read-only

List every WordPress plugin with active status, version, author, and available updates. Read-only alternative to install or activation tools, requiring manage_options access.

Instructions

[UNIFIED] List every plugin known to WordPress with active/network-active status, version, author, and update availability. Read-only (no install/activate). Requires Airano MCP Bridge v2.11.0+ and a WordPress user with manage_options.

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_specialist_wp_plugin_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation the description adds real operational context: the Airano MCP Bridge v2.11.0+ prerequisite and the manage_options capability needed. It stops short of saying whether the full plugin set is returned at once or how failures (e.g. bridge too old) surface.

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?

Three tight sentences with no filler: the operation and return fields are front-loaded, the read-only boundary and prerequisites follow. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only single-purpose list tool with no output schema, the description does the work of enumerating return fields and stating environment requirements. Only the unexplained 'site' parameter keeps it from being fully self-sufficient.

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?

The single required parameter 'site' has 0% schema description coverage, and the description never explains its expected form (site ID, slug, or URL) or whether it must match a configured connection. With the schema providing no help, this is the definition's main gap.

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?

States a specific verb (List) and resource (WordPress plugins) plus the scope 'every plugin known to WordPress' and the exact fields returned (active/network-active status, version, author, update availability). The parenthetical '(no install/activate)' explicitly separates it from the plugin_install_*, activate, and update siblings.

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

Usage Guidelines4/5

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

The read-only framing and '(no install/activate)' note tell an agent this is the inspection path rather than the mutation path, and the manage_options requirement sets the precondition. It does not name a specific alternative to use for mutation, but the exclusions give clear selection context.

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