Skip to main content
Glama

mcp_list_taxonomies

Lists all public WordPress taxonomies for a site, including names, labels, hierarchy, post types, REST base, and term counts.

Instructions

List all public taxonomies (name, labels, hierarchical, post_types, rest_base, term count)

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "site"
      +]
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the scope (public taxonomies only, implying private ones are excluded) and the exact field set returned, but says nothing about authentication, pagination, or ordering, and the read-only nature is only implied by "List".

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?

One front-loaded sentence with no filler; the field list is compressed into a parenthetical. It is terse to the point of omitting usage context, but every word present earns its place.

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 single-parameter list tool with no output schema, enumerating the returned fields in the description compensates well for the absent output schema. The only shortfall is the missing note on result size/pagination, which matters for a 'list all' call.

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 100% with a single required 'site' parameter already documented as "Site id (see list_sites)". The description adds no meaning beyond that, so the baseline of 3 applies; there is nothing missing but nothing gained either.

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?

Specific verb (List) plus resource (public taxonomies), with the returned fields enumerated in parentheses so the agent knows exactly what comes back. It does not explicitly contrast itself with the nearby mcp_list_post_types sibling, so an agent must infer the taxonomy/post-type distinction from domain knowledge.

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 statement of when to call this versus alternatives, nor prerequisites; the only scoping hint is the word "public". An agent reading this alone learns what it returns but not when it is the right choice over mcp_list_post_types or mcp_list_terms.

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