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

WordPress Plugin Directory MCP Server

by juanma-wp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

download_plugin

Download any WordPress plugin by providing its slug. Specify an optional version to retrieve a specific release.

Instructions

Download a plugin from WordPress.org

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

Input Schema

NameRequiredDescriptionDefault
slugYesPlugin slug to download
versionNoPlugin version (default: "latest")latest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

C2.8/5.0
Behavior1/5

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

With no annotations and no output schema, the description fails to disclose what the tool returns (e.g., file content, binary data, or a link) or any side effects, leaving the agent uninformed about behavior.

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 sentence with no fluff, achieving concise communication, though it could be slightly more structured.

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

Completeness1/5

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

Given no output schema, the description should explain return formats or error handling; it does not, making the tool incomplete for effective use.

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 coverage is 100% with descriptions for both parameters, so the description adds no extra meaning beyond the schema, resulting in a baseline score.

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 verb 'Download' and the resource 'plugin from WordPress.org', which distinguishes it from sibling tools like search_plugins or get_plugin_info, which have different purposes.

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 on when to use this tool versus alternatives such as search_plugins or get_plugin_info, nor any prerequisites (e.g., need for a plugin slug from search).

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