Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: List taxonomy terms

wordpress_list_taxonomy_terms
Read-only

List terms from any registered WordPress taxonomy—categories, tags, or custom taxonomies—with filtering by parent, empty status, and pagination.

Instructions

[UNIFIED] List terms of a specific taxonomy. Works with any registered taxonomy including categories, tags, and custom taxonomies.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
siteYes
parentNo
per_pageNo
taxonomyYes
hide_emptyNo

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

C2.9/5.0
Behavior2/5

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

readOnlyHint=true already declares the safety profile, so the description only needs to add operational context beyond that. It contributes little: nothing about default page size, whether parent/hide_empty filtering applies, how results are ordered, or how much data is returned — gaps that matter for a paginated list tool with six parameters.

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 tight sentences with the scope statement front-loaded and no filler. Its brevity is appropriate, though it is short because it omits information rather than because it is optimally dense.

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?

For a six-parameter, read-only listing tool with no output schema and no annotation coverage of filtering or pagination, the description leaves the most consequential parameters (parent, hide_empty, per_page) opaque. An agent cannot determine how to narrow or size the result set from this definition.

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?

Schema description coverage is 0% with six parameters, so the description must carry the burden and does not. It mentions the concept of taxonomy but explains none of page, per_page, parent, hide_empty, or site semantics — an agent would be guessing at filtering and pagination behavior.

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 gives a specific verb and resource ("List terms of a specific taxonomy") and explicitly notes it covers categories, tags, and custom taxonomies, which implicitly distinguishes it from the specialized wordpress_list_categories and wordpress_list_tags siblings. It stops short of naming those siblings as alternatives, so the differentiation is inferential rather than explicit.

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?

"Works with any registered taxonomy" implies this is the general-purpose choice, but there is no explicit when-to-use versus wordpress_list_categories/wordpress_list_tags guidance, no mention of pagination strategy, and no prerequisites (auth/site requirements) stated.

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