Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_create_taxonomy_term

Creates a new taxonomy term in WordPress, specifying name, slug, parent, and description to organize content by category or custom taxonomy.

Instructions

Create a term in a taxonomy

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": {
      "taxonomy": "<taxonomy>",
      "name": "<name>"
    },
    "name": "wp_create_taxonomy_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
slugNo
parentNoParent term ID (categories only)
taxonomyYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the mutation. It does not explain behavior on duplicate terms, whether slug is auto-generated, permission requirements, or how parent/child relationships are handled, leaving significant behavioral unknowns.

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?

The description is a single sentence with no wasted words, making it easy to parse. It is under-specified, but the conciseness itself is appropriate for such a brief statement.

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?

Given five parameters, no annotations, and no output schema, the description is too sparse to fully support correct invocation. It omits how taxonomy should be specified, how this relates to category/tag creation tools, and what happens after creation.

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 only 20%, and the tool description adds no parameter-level meaning. The parent parameter is explained in the schema, but taxonomy, name, slug, and description are left to the agent to infer from their names alone.

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 names a clear verb ('Create') and a specific resource ('a term in a taxonomy'), so an agent understands the basic action. However, it does not differentiate this from sibling tools like wp_create_category and wp_create_tag, which also create taxonomy terms in WordPress, leaving some ambiguity about scope.

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?

There is no guidance about when to use this tool versus alternatives such as wp_create_category or wp_create_tag. The description does not mention custom taxonomies, built-in taxonomy handling, or any conditions that would make this tool the preferred choice.

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