Retrieve all channels within a specified category by its ID. Useful for managing or auditing Discord server organization.
List all channels grouped under a specific category
| Name | Required | Description | Default |
|---|---|---|---|
| categoryId | Yes | Category ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'List' implies a read operation, but nothing is said about permissions required, ordering, pagination, or whether it includes sub-channels or only top-level ones.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence with no padding, and the scoping constraint (per category) is front-loaded. Adequately sized for a simple one-parameter list tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list tool with no output schema this is minimally adequate, but behavioral gaps like ordering and pagination remain, and no sibling differentiation is offered in a dense tool namespace.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and only one parameter (categoryId) exists, so the schema does the documenting. The description's phrase 'a specific category' reinforces the parameter's role but adds no syntax or format detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (list) and resource (channels) scoped to a category, which is clear. It does not distinguish itself from siblings like list_channels or find_channel, so an agent must infer the difference from names alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or when-not-to-use guidance. The description does not mention list_channels (all channels) or find_channel as alternatives, even though those siblings overlap heavily.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.