Skip to main content
Glama

create_category

Creates a new WordPress category from a required name, with optional slug, parent ID, and description for organizing posts.

Instructions

Create a new WordPress category

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

Input Schema

NameRequiredDescriptionDefault
nameYesCategory name
slugNoCustom slug (optional, e.g. an ASCII slug for non-ASCII names)
parentNoParent category ID (optional)
descriptionNoCategory description (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the mutation/safety profile is covered. The description adds nothing beyond that: no mention of duplicate handling, whether the new category is returned with an ID, or side effects on hierarchy, which is the meaningful gap for a create tool.

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?

A single front-loaded clause with no padding or redundancy. It is efficient, though the brevity reflects under-specification rather than disciplined compression.

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 four-parameter create tool with no output schema, the description should say at least what is returned and how collisions with existing categories are treated. The fully documented schema and present annotations offset some of this, but the description is thin relative to a write operation.

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 description coverage is 100%, so name, slug, parent, and description are all documented in the schema, including the useful hint about ASCII slugs for non-ASCII names. Baseline 3 applies since the description adds no further meaning beyond the structured fields.

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 states a specific verb and resource ('Create a new WordPress category'), which is unambiguous about the operation. It does not differentiate from siblings such as create_tag or create_post, relying on the resource noun alone to distinguish, but the core purpose is clear.

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 on when to use this instead of create_tag or create_post_with_categories_tags, nor any prerequisite (authentication, permission level) or note about behavior when a category with the same name already exists. The agent receives no conditions or exclusions.

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