wordpress_get_theme_modsRetrieve theme customizer settings from Appearance → Customize. Access and manage theme modifications for your WordPress site.
Get theme customizer settings (Appearance → Customize data)
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It hints at the data source (Appearance → Customize) but does not disclose return format, side effects (e.g., safety, permissions), or any behavioral nuance beyond the simple 'get' operation. This is minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, concise sentence with no fluff or redundancy. It is front-loaded and immediately clear what the tool does.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (no params, no output schema), the description gives the essential purpose. However, it lacks any mention of what the returned data looks like or how it relates to other theme settings tools, making it only partially complete for an agent that must choose among many similar getters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the input schema is already complete. With a baseline of 4 for no parameters, the description does not need to add parameter details, and it doesn't.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves theme customizer settings, with a specific verb and resource. It does not distinguish it from sibling tools like get_theme_json or get_global_styles, but 'theme mods' is a distinct concept that is adequately understood.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The description only implies usage for fetching Appearance → Customize data, but without explicit context, when-not-to-use, or alternative references, it leaves the agent without decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.