Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_list_customizer_settings

Read-onlyIdempotent

Discover registered, accessible active-theme Customizer settings before using CSS to override native theme layout. For Astra Header Builder, search for header-desktop-items or header-mobile-items. Supports top-level theme mods and indexed astra-settings options when Astra is the active parent theme, not arbitrary plugin options. Results are bounded and contain IDs, not values; use wp_get_customizer_setting before editing.

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_id": "<site_id>"
    },
    "name": "wp_list_customizer_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
searchNoOptional case-insensitive substring of the setting ID.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are bounded, they return IDs rather than values, and only top-level theme mods plus indexed astra-settings are included. It stops short of explaining how limit/offset bound the result set or what ordering to expect.

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?

Four front-loaded sentences that each carry distinct information: purpose, the Astra search hint, the supported-scope limits, and the return/next-step contract. Slightly dense, with the Astra token example being the most niche line, but nothing is redundant.

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 four-parameter read tool with no output schema, the description does the important work of stating what comes back (IDs, not values) and what to call next. The remaining gap is paging semantics for limit/offset, which neither schema nor description resolves.

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 50%: site_id and search are documented in the schema, while limit and offset are bare with only min/max. The description's 'results are bounded' hints at paging but never maps it to limit/offset or explains behavior at the 100 cap, so it only partially compensates for the uncovered half.

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 opens with a specific verb and resource ('Discover registered, accessible active-theme Customizer settings') and immediately scopes it (active theme, not arbitrary plugin options), which separates it from wp_list_options and wp_list_theme_mods. It also names the legitimate follow-up tool, wp_get_customizer_setting, so the agent can distinguish list from 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 gives an explicit trigger ('before using CSS to override native theme layout'), an explicit exclusion ('not arbitrary plugin options'), and an explicit next step ('use wp_get_customizer_setting before editing'). The Astra-specific search hint (header-desktop-items / header-mobile-items) is concrete, actionable routing guidance rather than vague advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources