Skip to main content
Glama

Create WordPress category

create_wordpress_category

Create a category on a connected WordPress site and return {id, name, slug, created}; created=false means a category with that name already existed (no duplicate is made). Use the id in create_post categories. 403 means the WordPress user connected to Flomixy may not create categories (WORDPRESS_TERM_CREATE_FORBIDDEN). Only create what the user asked for: check list_wordpress_categories first. Requires scope ACCOUNTS_WRITE (a key issued before that scope existed must be re-issued).

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

Input Schema

NameRequiredDescriptionDefault
nameYesCategory name, 1-200 characters. An existing name (case-insensitive) is returned as is, never duplicated.
parentNoParent category id (from list_wordpress_categories) to create a sub-category. Omit for a top-level category.
accountIdYesThe WordPress site account id (list_accounts, channel WORDPRESS).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses idempotency semantics (created=false, no duplicate made), the 403 failure mode with its WORDPRESS_TERM_CREATE_FORBIDDEN code, and the ACCOUNTS_WRITE scope requirement including the stale-key re-issue caveat. This is far beyond a bare mutation statement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads action and return shape, then layers idempotency, error meaning, cross-tool linkage, guardrail, and auth requirement in short, non-redundant clauses. No sentence is filler despite the density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter mutation with no output schema and no annotations, the description supplies the return shape, idempotency behavior, permission failure semantics, and auth scope. Nothing an agent needs in order to call it correctly appears to be missing.

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 coverage is 100%, so name, parent, and accountId are already documented, and the description adds no syntax or format detail beyond them. Its only added semantic is cross-tool (the returned id feeds create_post categories), which is about output rather than input parameters, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 category on a connected WordPress site") and immediately describes the return shape {id, name, slug, created}. It is clearly distinguishable from the sibling create_wordpress_tag and from list_wordpress_categories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: check list_wordpress_categories first, only create what the user asked for, and use the returned id in create_post categories. Both the when-to-use and the follow-up action are named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources