Add a new term to any taxonomy, with options for name, slug, description, and parent term.
Create a term in any taxonomy
| Name | Required | Description | Default |
|---|---|---|---|
| taxonomy | Yes | Taxonomy name | |
| name | Yes | Term name | |
| slug | No | URL slug | |
| description | No | Term description | |
| parent | No | Parent term ID (for hierarchical taxonomies) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, yet description only states creation. Does not disclose behavior for duplicate terms, validation, required capabilities, or side effects.
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?
Single sentence is concise but overly brief; could include structured details or typical usage patterns.
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?
Description lacks context about return values, error handling, and relationship to other taxonomy tools. With many sibling tools and no output schema, more detail is needed.
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?
Schema covers all 5 parameters with descriptions, so no additional details are needed. Description adds no value beyond schema.
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?
Description clearly states 'Create a term in any taxonomy', specifying verb, resource, and scope. Distinguishes from sibling tools like mcp_update_term and mcp_delete_term.
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?
No guidance on when to use this tool vs alternatives (e.g., mcp_assign_terms, woo_create_attribute_term). No prerequisites or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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