Skip to main content
Glama

mcp_list_terms

Retrieve terms from any WordPress taxonomy, including categories, tags, and custom taxonomies. Filter by empty status, parent ID, or search term to get specific lists.

Instructions

List terms for any taxonomy (categories, tags, custom taxonomies)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taxonomyYesTaxonomy name
hide_emptyNoHide terms with no posts
parentNoParent term ID (for hierarchical)
searchNoSearch term names
Behavior2/5

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

No annotations provided, so description carries full burden. Only states 'List terms', implying a read operation but lacks details on pagination, safety, or other behaviors.

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?

Single sentence, front-loaded with verb and resource, no wasted words. Highly efficient.

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?

No output schema, so description should provide insight into return format. It does not. Also lacks information on ordering, pagination, or how to use optional parameters effectively.

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%, so baseline is 3. Description doesn't add meaning beyond schema parameter descriptions; it merely restates the purpose.

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 clearly states the action (list), resource (terms), and scope (any taxonomy). It distinguishes from sibling tools like mcp_list_taxonomies and term CRUD tools.

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?

No guidance on when to use this over specialized tools like wp_list_categories or woo_list_categories. The description implies it's a general term lister but does not provide context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cvrt-jh/wordpress-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server