Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Create category

wordpress_create_category

Create a new WordPress category with optional parent hierarchy, description, language, and translation settings.

Instructions

[UNIFIED] Create a new WordPress category. Supports hierarchical categories with parent relationships.

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>",
      "name": "<name>"
    },
    "name": "wordpress_create_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
siteYes
parentNo
languageNo
descriptionNo
translation_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.14.0
    • addedInput schema / properties / language
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / translation_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  2. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv3.4.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the bar is lower, but the description adds only the parent-hierarchy capability. It does not say what happens on a duplicate name (relevant given idempotentHint=false), whether the category is published immediately, or what auth/site scope is required.

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 short sentences, front-loaded with the action, with no filler. The '[UNIFIED]' tag is the only wasteful token, and the hierarchy note is placed logically after the core action.

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 6-parameter write tool with no output schema and zero schema descriptions, the definition is too thin: return shape, duplicate handling, and the language/translation_of semantics are all unaddressed. An agent would have to guess on half the parameters.

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% across 6 parameters, so the description carries the full burden, yet it only gestures at 'parent' and says nothing about site, language, description, or translation_of. Those latter two are non-obvious (likely multilingual-plugin fields) and an agent cannot resolve them from the name 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?

States a specific verb and resource: 'Create a new WordPress category.' The scope is clear enough to distinguish it from wordpress_delete_category and wordpress_update_category, though the '[UNIFIED]' prefix is unexplained jargon that adds no meaning for an agent.

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 when-to-use guidance is offered: nothing says when to pick this over wordpress_create_tag or woocommerce_create_product_category, and no prerequisites (permissions, site selection) are mentioned. The agent must infer context entirely.

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