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

WordPress Plugin Directory MCP Server

by juanma-wp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_plugins

Search WordPress.org plugins by keyword to find and retrieve plugin details for your site.

Instructions

Search for WordPress.org plugins by keyword

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": {
      "query": "<query>"
    },
    "name": "search_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query for plugins
limitNoMaximum number of results (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It mentions 'search by keyword' but omits details like result format, pagination (if any), whether the search is case-sensitive, or any authentication requirements. For a public API tool, this is a significant gap.

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?

The description is a single, well-formed sentence that uses active voice and is free of unnecessary words. It efficiently conveys the core purpose without redundancy.

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 keyword search tool with two parameters, the description is adequate but minimal. It does not explain the return value (e.g., list of plugin names, slugs, or full objects), nor does it address edge cases like empty results or rate limits. Given the lack of an output schema, more detail would be helpful.

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?

The schema already covers both parameters (query and limit) with descriptions. The description adds minimal value by confirming 'query' is a keyword search. With 100% schema coverage, baseline is 3, and the description does not significantly enhance understanding beyond what the schema provides.

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 action ('Search') and the resource ('WordPress.org plugins'), with a specific method ('by keyword'). This effectively distinguishes it from sibling tools like 'get_plugin_info' (which retrieves details for a known plugin) or 'compare_plugins'.

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 description implies the tool is for finding plugins based on keywords, but it does not explicitly state when to use it over alternatives (e.g., when you have a specific plugin name, use 'get_plugin_info'). No guidance on when not to use it or what to do if the search is too broad.

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