Skip to main content
Glama
Sign In
wpxmcp

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a plugin

get_plugin
Read-only

Retrieve complete details for an installed WordPress plugin using its plugin file path, such as woocommerce/woocommerce, to inspect version, status, and more.

Instructions

Get full details about one installed plugin by its plugin file path, e.g. "woocommerce/woocommerce" or "hello-dolly/hello".

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": {
      "plugin": "<plugin>"
    },
    "name": "get_plugin"
  }
}

Input Schema

NameRequiredDescriptionDefault
pluginYesPlugin identifier as returned by list_plugins, e.g. "akismet/akismet" (no .php extension).
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the plugin path identification pattern but does not explain what 'full details' includes, return format, or any read-time caveats.

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?

A single, front-loaded sentence that names the action and resource, then gives immediate useful examples. No filler or repetition.

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?

The tool is simple and the schema is strong, so an agent with the plugin identifier can invoke it. However, the lack of an output schema and the vague 'full details' phrase leave the return expectations underspecified, and sibling ambiguity with get_plugin_info/inspect_plugin is not resolved.

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 input schema already provides 100% parameter coverage with detailed descriptions, including the plugin identifier format and site_id default behavior. The description adds redundant but helpful path examples, yet does not substantially extend the schema's meaning.

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 ('Get full details') and the resource ('one installed plugin'), and specifies the identifying input format with concrete path examples. It distinguishes itself from broad listing/searching sibling tools, though it does not explicitly differentiate from similarly named siblings like get_plugin_info or inspect_plugin.

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?

Usage is implied: use this when you need full details for a single installed plugin and know its plugin file path. There is no explicit guidance about when to prefer list_plugins, search_plugins, or get_plugin_info, and no mention of exclusions or alternatives.

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