discp

delete_category

Remove a Discord channel category by ID, leaving its channels unparented. Provide an optional audit log reason to document the deletion.

Instructions

Delete a channel category (channels inside will become unparented)

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

Input Schema

Name	Required	Description	Default
`reason`	No	Audit log reason
`categoryId`	Yes	Category ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses one important side effect — contained channels become unparented rather than deleted — but says nothing about irreversibility, required permissions, or whether the operation can be undone.

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?

A single sentence with the action front-loaded and the side effect in a compact parenthetical. Every element earns its place.

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

Completeness4/5

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

For a small two-parameter delete tool with full schema coverage and no output schema, the description covers the essential operation and its key side effect. Only auth/irreversibility details are absent.

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 both parameters (categoryId, reason) are already documented in the schema. The description adds nothing about parameter formats or constraints, so the baseline 3 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?

States a specific verb and resource ('Delete a channel category'), which is unambiguous. It does not explicitly distinguish itself from siblings like edit_category or delete_channel, but the destructive scope is clear from the verb alone.

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 versus edit_category or delete_channel, nor any prerequisites (e.g. permissions needed). The parenthetical warns of a side effect, which is useful context but not usage routing.

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

Deploy Server