Skip to main content
Glama
Sign In
wordpress-mcp-server

wordpress-mcp-server

by bgildea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List plugins

list_plugins
Read-only

Fetch installed WordPress plugins with version and active status; requires an administrator account.

Instructions

List installed plugins with version and active status. Requires an administrator account.

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": "list_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the meaningful auth constraint (administrator account) and the fields returned, but says nothing about result volume, pagination, or whether inactive plugins are included.

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?

Two short sentences, zero waste, with the output content front-loaded before the access constraint. Nothing is repeated from the name or title.

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 zero-parameter read-only listing with no output schema, the description covers what is returned and the access requirement, which is enough for correct invocation. Only minor gaps remain, such as whether inactive plugins are included or results are paginated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description needs to compensate for. The description correctly implies the call is unfiltered and returns all installed plugins.

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?

States a specific verb and resource ('List installed plugins') plus the payload contents ('version and active status'), so an agent knows exactly what comes back. It does not differentiate against siblings, but the sibling names (list_posts, get_post, get_site_info) cover unrelated resources, so no confusion is likely.

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 definition supplies a prerequisite ('Requires an administrator account'), which tells the agent when the call will succeed, but gives no explicit when-to-use versus when-not guidance and names no alternative. Usage is only implied by the resource name.

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