Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: List taxonomies

wordpress_list_taxonomies
Read-only

List all registered WordPress taxonomies, including built-in and custom ones, with their configuration and post type associations to inspect how content types are organized.

Instructions

[UNIFIED] List all registered taxonomies including built-in (category, post_tag) and custom taxonomies. Returns configuration and post type associations.

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

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description's main contribution is "Returns configuration and post type associations," which usefully indicates the payload shape despite no output schema. It says nothing about result size, pagination, or scope (site-wide vs filtered), so the added behavioral context is modest.

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?

Two compact sentences, front-loaded with the core action and followed by enabling detail about built-ins and return contents. No filler wording, though the "[UNIFIED]" prefix carries no meaning for an agent selecting the tool.

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

Completeness3/5

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

For a simple read-only list tool with annotations covering safety and the description covering return contents, the core is covered. The undocumented "site" parameter is the notable remaining hole for an agent trying to invoke it correctly.

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?

The single required parameter "site" has 0% schema description coverage, and the description never explains whether it expects a URL, slug, or ID, nor whether it selects a site in multisite setups. The description provides no meaning beyond the bare 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?

"List all registered taxonomies including built-in (category, post_tag) and custom taxonomies" states a specific verb and resource, and clarifies that this returns taxonomy definitions rather than terms. It does not explicitly name the overlapping siblings (wordpress_list_categories, wordpress_list_tags, wordpress_list_taxonomy_terms), so differentiation is left to inference.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the discovery/metadata call that should precede term listing. There is no explicit statement of when to prefer this over the many sibling list tools, and no prerequisites (e.g. authentication) are mentioned.

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