Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List taxonomy terms

list_terms
Read-only

List taxonomy terms with search, ordering, hierarchy filtering, and pagination. Works for categories, tags, and custom taxonomies to find the right terms for your WordPress site.

Instructions

List terms in any taxonomy with search, ordering, hierarchy filtering and pagination. Works for categories, tags and custom taxonomies alike.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoWhich page of results to return.
postNoOnly terms assigned to this content ID.
slugNoFilter by exact slug.
orderNoSort direction.asc
parentNoOnly direct children of this term ID. Hierarchical taxonomies only.
searchNoMatch against term names.
orderbyNoWhich field to sort by.name
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
per_pageNoHow many results per page.
taxonomyNoTaxonomy slug or REST base (category, post_tag/tags, or a custom one).category
hide_emptyNoSkip terms with no content assigned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / parent / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / parent / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / post / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / post / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds scope and feature context (search, ordering, hierarchy filtering, pagination) but does not disclose additional behavioral details such as response shape or default taxonomy behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with no redundancy. The core purpose is front-loaded and the taxonomy scope is stated immediately, making it quick for an agent to parse.

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?

Given the rich schema with 11 well-described optional parameters and safe read-only annotations, the description is adequate for a list operation. It could mention pagination defaults or output shape, but those are either low-risk or inferable from the schema.

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 the schema fully documents each parameter. The description's mention of 'search, ordering, hierarchy filtering and pagination' provides a useful conceptual grouping, but it adds no parameter details beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('List') and resource ('taxonomy terms'), and clearly distinguishes the scope from siblings like get_term by noting it works 'in any taxonomy' including categories, tags, and custom taxonomies. This leaves no ambiguity about what the tool does.

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

Usage Guidelines4/5

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

The description provides clear context: use this when you need to list terms across any taxonomy, including custom ones. It does not explicitly name alternatives or exclusion criteria, but the use case is evident from the description.

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