Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp option get

wordpress_specialist_wp_option_get
Read-only

Reads a single WordPress option by name while blocking credential-like keys such as passwords, tokens, and salts. Use it to inspect site settings safely without exposing sensitive data.

Instructions

[UNIFIED] Read a single WordPress option by name. Refuses keys that look like credentials (suffix matches secret/password/api_key/token/auth_key/auth_salt etc.) — operators can still inspect those via wp-admin if needed. Requires Airano MCP Bridge v2.11.0+ and manage_options.

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": {
      "site": "<site>",
      "name": "<name>"
    },
    "name": "wordpress_specialist_wp_option_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond readOnlyHint=true, it discloses a suffix-based credential refusal policy, an operator fallback, the minimum Airano MCP Bridge version, and the required manage_options capability. These details materially affect whether calls succeed and how sensitive-option requests should be handled.

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 purpose is front-loaded, followed by the principal exclusion and then the operational prerequisites. Three compact sentences each contribute distinct, useful information 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?

For a simple two-argument read, the description covers scope, refusal behavior, and prerequisites unusually well. With no output schema and no schema parameter descriptions, however, the site identifier format and result or not-found behavior remain unspecified.

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

Parameters2/5

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

With 0% schema description coverage, the description only partially compensates: name is identified as a WordPress option key and its credential-related restrictions are explained. The required site parameter remains entirely undocumented, including whether it expects an ID, URL, domain, or configured site alias.

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?

“Read a single WordPress option by name” gives a specific verb, resource, cardinality, and lookup method. It does not explicitly differentiate this generic option reader from specialized siblings such as wp_reading_settings_get or wp_site_identity_get.

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

Usage Guidelines5/5

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

It defines the single-named-option use case, explicitly excludes credential-like keys, and provides wp-admin as the fallback for inspecting those keys. Although it does not route among specialized sibling readers, its own when/when-not guidance and alternative are explicit.

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