Skip to main content
Glama

mcp_list_terms

Retrieve WordPress taxonomy terms, including categories, tags, and custom taxonomies, with IDs, names, slugs, descriptions, parents, and post counts. Filter by parent, search text, or empty status.

Instructions

List terms for any taxonomy (categories, tags, custom taxonomies): id, name, slug, description, parent, 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>",
      "taxonomy": "<taxonomy>"
    },
    "name": "mcp_list_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
parentNoOnly direct children of this term ID (0 = top level)
searchNoSearch term names
taxonomyYesTaxonomy name (e.g. category, post_tag, product_cat)
hide_emptyNoHide terms with no posts (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv3.14.0
    • removedInput schema / properties / hide_empty / default
      Removed value: -false
    • changedInput schema / properties / hide_empty / description
      Previous value: -"Hide terms with no posts"New value: +"Hide terms with no posts (default false)"
    • changedInput schema / properties / parent / description
      Previous value: -"Parent term ID (for hierarchical)"New value: +"Only direct children of this term ID (0 = top level)"
    • addedInput schema / properties / parent / minimum
      Added value: +0
    • changedInput schema / properties / parent / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / taxonomy / description
      Previous value: -"Taxonomy name"New value: +"Taxonomy name (e.g. category, post_tag, product_cat)"
    • addedInput schema / properties / taxonomy / pattern
      Added value: +"^[a-zA-Z0-9_-]+$"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "taxonomy"
      -]New value: +[
      +  "site",
      +  "taxonomy"
      +]
  3. 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 has to carry the burden of behavioral disclosure. The verb 'List' implies a read-only operation, and the description usefully enumerates the fields returned (id, name, slug, description, parent, count), which compensates for the missing output schema. It says nothing about pagination, ordering, permissions, or result-size limits.

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 front-loaded sentence with a compact colon-delimited list of returned fields. Nothing is wasted, although the field list could be structured more clearly.

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?

Five parameters, no annotations, and no output schema make this a moderately complex definition. Enumerating the returned fields covers the missing output schema, and the schema fully documents the inputs. Only minor gaps, such as pagination limits and ordering behavior, remain.

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 every parameter (site, taxonomy, parent, search, hide_empty) is already documented in the schema, which sets a baseline of 3. The description adds no further meaning for any parameter and does not explain how the filters combine or interact.

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?

States a specific verb and resource ('List terms'), broadens the scope ('any taxonomy') with concrete examples (categories, tags, custom taxonomies), and enumerates the returned fields. It is distinguishable from the sibling 'mcp_list_taxonomies', which lists the taxonomies themselves rather than their terms, though the sibling is not named.

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 explicit guidance about when to choose this tool instead of alternatives. The phrase 'for any taxonomy' implies it is the general-purpose term lister and gives a hint about correct use, but exclusions and cross-references to siblings such as 'mcp_list_taxonomies' or 'woo_list_attribute_terms' are absent.

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