Skip to main content
Glama
Sign In
wpxmcp

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Read a plugin's settings option

get_plugin_settings
Read-only

Read a WordPress plugin's stored settings as JSON, with passwords and tokens redacted. Omit the option name to list the plugin's settings before choosing one.

Instructions

Read an option a plugin owns, unserialised into JSON, with obvious secrets (keys matching pass/secret/token/api_key/license) redacted to "••••" plus the last four characters. Omit option to list the options the plugin appears to own so you can pick one. This reads the raw stored option — the same data the plugin's settings screen edits.

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_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionNoThe option name to read, e.g. "wpseo_titles". Omit to list the plugin's likely options.
pluginYesPlugin identifier (slug, dir/file, or name).
revealNoReturn secret values in the clear instead of redacting them. Use sparingly.
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. Addedv2.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses important behavior: secrets matching pass/secret/token/api_key/license are redacted to '••••' plus the last four characters, the response is unserialised JSON, and omitting `option` lists owned options. It also notes the data is the raw stored option, giving agents an accurate mental model of what they are reading.

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?

Three short sentences deliver the core behavior, the list-mode option, and the raw-data clarification. Every clause earns its place and the most important information is front-loaded without repetition.

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?

Given the moderate complexity, read-only annotations, and lack of an output schema, the description covers the essential call pattern: required plugin, optional option, listing mode, and redaction behavior. It stops just short of a 5 because it does not describe the exact shape of the listing response or error cases, though those are not critical for a straightforward read.

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 documents each parameter's role. The description adds the redaction format and reinforces the omit-to-list behavior, but it does not add significant meaning beyond the input schema. A baseline 3 is appropriate since the schema carries the load.

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 states a specific verb and resource: reading an option a plugin owns, decoded from raw storage into JSON. It also exposes a distinctive behavior—listing a plugin's likely options when `option` is omitted—which clearly separates it from generic get_options-style tools. The scope is precise enough that an agent knows exactly what this tool does without reading siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage context: omit `option` to discover candidates, and read the raw stored value just as the plugin's settings screen edits it. It does not explicitly name alternatives or when-not-to-use cases, but the read-only scope and plugin-option focus make the intended use apparent.

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