Skip to main content
Glama
Sign In
WordPress Plugin Directory MCP Server

WordPress Plugin Directory MCP Server

by juanma-wp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_plugin_files

List files within a WordPress plugin directory, with optional filter by file extension.

Instructions

List files in an extracted plugin

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": {
      "slug": "<slug>"
    },
    "name": "list_plugin_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPlugin slug
extensionNoFilter by file extension (e.g., ".php", ".js")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

C2.9/5.0
Behavior2/5

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

Without annotations, the description carries full responsibility. It only says 'list files' without specifying output format, recursion depth, or whether it returns full paths. Minimal behavioral disclosure.

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?

The description is a single short sentence, which is efficient and easy to read. It could include more detail without being verbose, but it is appropriately concise.

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

Completeness2/5

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

The tool has two parameters and no output schema. The description does not explain what is returned (e.g., file names, paths, recursive listing) or how the extension filter works. Lacks completeness for a list operation.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains both parameters. The tool description does not add extra meaning beyond what is in the schema.

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?

The description clearly states the action (list) and the resource (files in an extracted plugin). It is distinct from sibling tools like read_plugin_file or get_plugin_info, though it does not explicitly differentiate.

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?

No guidance is provided on when to use this tool versus alternatives. The description implies usage after extraction but lacks explicit context or exclusions.

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