discord-mcp

discord_list_channels

Read-onlyIdempotent

List a Discord server's channels and categories, optionally filtered by type or name, to find channel IDs before reading or posting. Returns markdown or JSON; threads excluded.

Instructions

List a server's channels and categories, optionally filtered by kind or name.

The usual way to find a channel_id before reading or posting. Threads are not
included — use discord_list_threads.

Returns: Markdown table (name, type, ID, category, topic) or JSON list of channel objects
with id, name, type, parent_id, position, topic.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Only return channels of this kind.
`guild_id`	No	Server (guild) ID. Omit to use DISCORD_GUILD_ID from .env.
`name_contains`	No	Case-insensitive substring filter on the name, e.g. 'general'.
`response_format`	No	'markdown' for reading, 'json' for full structured data.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description still adds real value beyond that by stating the threads exclusion and the exact return shape. It stops short of richer context (pagination, auth scope, ordering guarantees), so a 4 rather than a 5.

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?

Three short, front-loaded sentences: purpose, routing hint, then return contract. No filler, and the most decision-relevant facts (what it lists, the threads caveat, the return format) come first.

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 read-only list tool with full schema coverage and an output schema, the description covers everything an agent needs: scope, the sibling alternative, and a summary of the return shape. Nothing essential is 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 description coverage is 100%, so the baseline is 3. The description references kind and name filtering, which loosely map to the 'type' and 'name_contains' parameters, but the schema already documents each field with examples and patterns, so the description adds little beyond it.

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?

The first sentence gives a specific verb and resource ('List a server's channels and categories') plus the scope of optional filtering. It also explicitly distinguishes itself from discord_list_threads ('Threads are not included'), so an agent can differentiate it from siblings without opening a schema.

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?

It states the primary use case explicitly ('The usual way to find a channel_id before reading or posting') and names the alternative for the excluded case ('use discord_list_threads'). When-to-use and the contrasting tool are both spelled out.

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