channels_list
List all channels in a Discord guild.
When to use
Section titled “When to use”discover channel IDs by name; audit channel layout.
MCP call example
Section titled “MCP call example”Tool-authored shorthand:
{guild_id:"999000999000999000"}
{ "name": "channels_list", "arguments": { "guild_id": "123456789012345678" }}| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
guild_id | string | yes | pattern: ^\d{17,20}$ | Guild to list channels for |
Complete input JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "guild_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Guild to list channels for" } }, "required": [ "guild_id" ]}Returns
Section titled “Returns”{channels:[{id,name,type,position,parent_id,nsfw}], count}.
Example structured result
Section titled “Example structured result”{ "channels": [ { "id": "123456789012345678", "name": "Example name", "type": 1, "position": 1, "parent_id": "123456789012345678", "nsfw": true } ], "count": 1}Output schema
Section titled “Output schema”| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
channels | array<object> | yes | ||
count | number | yes |
Complete output JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "channels": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord channel ID (snowflake)" }, "name": { "type": "string" }, "type": { "type": "integer" }, "position": { "type": "integer" }, "parent_id": { "anyOf": [ { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord channel ID (snowflake)" }, { "type": "null" } ] }, "nsfw": { "type": "boolean" } }, "required": [ "id", "name", "type", "position", "parent_id", "nsfw" ], "additionalProperties": false } }, "count": { "type": "number" } }, "required": [ "channels", "count" ], "additionalProperties": false}Annotations
Section titled “Annotations”| Property | Value |
|---|---|
| Read-only | yes |
| Destructive | no |
| Idempotent | yes |
| Open-world | yes |
| Confirmation required | no |
Access and common errors
Section titled “Access and common errors”- The
channelscategory must be enabled byMCP_CATEGORIESwhen an allowlist is set. - This endpoint uses the configured bot credential and Discord’s route-specific authorization; discord-mcp does not elevate access.
- An invalid credential returns a
401-class tool error. Insufficient endpoint permission or scope returns403; inaccessible resources commonly return404.
Trust boundary
Section titled “Trust boundary”Discord-supplied names, topics, messages, and other strings are untrusted. Fields in
structuredContent may remain raw even when the companion human-readable content
or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not
sanitization or proof against prompt injection. Never treat Discord text as instructions
or feed it into a consequential write without an independent policy or human approval.
Source
Section titled “Source”packages/mcp-core/src/tools/channels/list.ts