Skip to main content
Glama

wp_list_themes

Lists all installed WordPress themes for a specified site, optionally filtering by active or inactive status to review available themes.

Instructions

List all installed themes

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": "wp_list_themes"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
statusNoLimit to these statuses

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.14.0
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status"New value: +"Limit to these statuses"
    • removedInput schema / properties / status / enum
      Removed value: -[
      -  "active",
      -  "inactive"
      -]
    • addedInput schema / properties / status / items
      Added value: +{
      +  "enum": [
      +    "active",
      +    "inactive"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / status / type
      Previous value: -"string"New value: +"array"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "site"
      +]
  3. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the full behavioral burden falls on the description, which says nothing about read-only safety, required permissions, or what the returned theme records contain. It also omits that a site context is mandatory in a multisite setup, which is the kind of operational detail this tool should disclose.

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?

A single four-word sentence with no filler and the resource front-loaded, which is efficient. It is arguably too sparse rather than bloated, but there is no wasted wording to penalize.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the only source of behavioral context, and it provides none beyond the one-line purpose. It does not mention the required site scoping or what a returned theme entry includes, which leaves an agent under-informed for a two-parameter list tool.

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 both `site` and `status` are already documented in the schema, and the baseline of 3 applies. The word "all" in the description is slightly at odds with the optional `status` narrowing parameter, but no additional semantics are offered beyond the schema.

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 pairs a specific verb ("List") with a specific resource ("installed themes"), so the agent knows exactly what the tool returns. It does not distinguish itself from the sibling mcp_search_themes, leaving the read-vs-filter distinction implicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no pointer to mcp_search_themes for filtered or query-based lookups. The agent must infer from the tool name alone when this enumeration is preferable to searching.

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