wordpress_get_termsRetrieve terms such as categories, tags, or custom taxonomy terms from a WordPress site. Specify the taxonomy to get its associated terms.
Get terms from a taxonomy (categories, tags, or custom)
| Name | Required | Description | Default |
|---|---|---|---|
| taxonomy | Yes |
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only restates the purpose and does not mention return format, pagination, error handling, permissions, or any other behavioral traits beyond a simple 'get' operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no redundant information. It is efficiently front-loaded and contains zero waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (one parameter, no output schema, no annotations), but the description is minimal. It explains the purpose and the taxonomy parameter, but omits details about the returned data structure or any edge-case behavior, leaving some gaps for the agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema only defines 'taxonomy' as a string with no description, so the description adds meaningful context by listing examples (categories, tags, custom). This helps the agent understand what values to pass, though it does not specify exact taxonomy slugs or format.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Get terms from a taxonomy' with examples covering categories, tags, and custom taxonomies. This specific verb and resource clearly distinguish it from sibling tools like wordpress_get_categories and wordpress_get_tags.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies that this tool can retrieve terms from any taxonomy, including categories, tags, or custom taxonomies. However, it does not explicitly contrast this with more specific tools like wordpress_get_categories or wordpress_get_tags, nor provide explicit when-to-use or when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.