Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Delete category

wordpress_delete_category
Destructive

Delete a WordPress category permanently or reassign its posts to another category.

Instructions

[UNIFIED] Delete a WordPress category. Can permanently delete or reassign posts to another 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": {
      "site": "<site>",
      "category_id": "<category_id>"
    },
    "name": "wordpress_delete_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
forceNo
category_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is known. The description adds genuinely useful context that deleting affects the category's posts rather than just the term itself, but it never says how reassignment is chosen (the schema has no target-category parameter) or whether deletion can fail.

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, no filler. The second sentence is necessary but vague enough that brevity costs some clarity.

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?

This is a destructive mutation with 0% schema coverage and no output schema, so the description carries the full disclosure burden. It omits what force=false actually does, what happens to posts (default category? reassignment to post's existing term?), and any failure modes, leaving the agent under-informed before an irreversible call.

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 0%, so the schema contributes no parameter meaning at all. The description implies a permanent-delete versus reassign branch that likely maps to the `force` flag, but it never names `force`, `site`, or `category_id`, and it does not state that reassignment happens automatically when force is false.

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 ("Delete a WordPress category") and adds the two outcome modes (permanent delete vs. reassign posts). It is clearly distinguishable from wordpress_delete_tag or wordpress_update_category by name, though it never explicitly contrasts them.

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 guidance on when to delete versus update/rename a category, and no condition explaining when to permanently delete versus reassign posts. The reader is left to infer that choice from a later tool call or from error behavior.

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