Skip to main content
Glama

update_category

DestructiveIdempotent

Updates an existing WordPress category's name, slug, parent, or description by category ID, letting you revise taxonomy details without creating a new category.

Instructions

Update an existing 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": {
      "category_id": "<category_id>"
    },
    "name": "update_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew category name (optional)
slugNoNew slug (optional; WordPress does not auto-update the slug when the name changes)
parentNoNew parent category ID (optional; use 0 to clear)
category_idYesCategory ID to update
descriptionNoNew category description (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether omitted fields are preserved, whether the slug is regenerated (only the schema hints at this), or what happens on an invalid category_id. For a destructive mutation this is a meaningful gap.

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

Conciseness3/5

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

It is a single front-loaded sentence with zero filler, so nothing is wasted. However the brevity crosses into under-specification rather than efficiency, leaving no room for the partial-update semantics that matter here.

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?

With five parameters, a destructive mutation flag, and no output schema, an agent needs to know that category_id is the anchor and that only supplied fields change. None of that is present, so the definition is incomplete relative to the tool's complexity.

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% and the schema itself documents each optional field, including the slug caveat and parent=0 to clear. The description repeats none of this and adds no new parameter meaning, so the baseline 3 for high schema coverage applies.

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 ('Update') and resource ('an existing WordPress category'), which is enough to separate it from create_category and delete_category. It stops short of naming the mutable fields or distinguishing it from siblings like update_tag/update_post, but the resource noun does the disambiguating work.

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?

'Existing' faintly implies this is not for creation, but there is no explicit when-to-use, no prerequisite (does the category need to exist / can partial updates be made?), and no routing to alternatives such as create_category. An agent must infer the correct context entirely.

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