discord-mcp

channels_list

Read-onlyIdempotent

List all channels in a Discord guild to discover channel IDs by name, audit channel layout, and inspect forum or media tags.

Instructions

Purpose: List all channels in a Discord guild.

When to use: discover channel IDs by name; audit channel layout and forum tags.

Example: {guild_id:"999000999000999000"}

Returns: {channels:[{id,name,type,position,parent_id,nsfw,available_tags?,applied_tags?}], count}. Forum/media tags include {id,name,moderated,emoji_id,emoji_name} when returned by Discord.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`guild_id`	Yes	Guild to list channels for

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "channels": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "id": {
-              "description": "Discord channel ID (snowflake)",
-              "pattern": "^\\d{17,20}$",
-              "type": "string"
-            },
-            "name": {
-              "type": "string"
-            },
-            "nsfw": {
-              "type": "boolean"
-            },
-            "parent_id": {
-              "anyOf": [
-                {
-                  "description": "Discord channel ID (snowflake)",
-                  "pattern": "^\\d{17,20}$",
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "position": {
-              "maximum": 9007199254740991,
-              "minimum": -9007199254740991,
-              "type": "integer"
-            },
-            "type": {
-              "maximum": 9007199254740991,
-              "minimum": -9007199254740991,
-              "type": "integer"
-            }
-          },
-          "required": [
-            "id",
-            "name",
-            "type",
-            "position",
-            "parent_id",
-            "nsfw"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "count": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "channels",
-      "count"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "channels": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "applied_tags": {
+              "description": "Tag IDs applied to a forum/media post, when returned by Discord",
+              "items": {
+                "pattern": "^\\d{17,20}$",
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "available_tags": {
+              "description": "Complete forum/media tags, including IDs, names, moderation and emoji fields, when returned by Discord",
+              "items": {
+                "additionalProperties": false,
+                "properties": {
+                  "emoji_id": {
+                    "anyOf": [
+                      {
+                        "pattern": "^\\d{17,20}$",
+                        "type": "string"
+                      },
+                      {
+                        "type": "null"
+                      }
+                    ]
+                  },
+                  "emoji_name": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "id": {
+                    "pattern": "^\\d{17,20}$",
+                    "type": "string"
+                  },
+                  "moderated": {
+                    "type": "boolean"
+                  },
+                  "name": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "id",
+                  "name",
+                  "moderated",
+                  "emoji_id",
+                  "emoji_name"
+                ],
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "id": {
+              "description": "Discord channel ID (snowflake)",
+              "pattern": "^\\d{17,20}$",
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "nsfw": {
+              "type": "boolean"
+            },
+            "parent_id": {
+              "anyOf": [
+                {
+                  "description": "Discord channel ID (snowflake)",
+                  "pattern": "^\\d{17,20}$",
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "position": {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            },
+            "type": {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "type",
+            "position",
+            "parent_id",
+            "nsfw"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "count": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "channels",
+      "count"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark this as read-only and idempotent, so the description does not need to repeat those. It adds valuable behavioral context by specifying the return shape, including optional forum/media tags with their nested fields, which goes beyond the schema.

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?

The description is well-structured with bolded sections for Purpose, When to use, Example, and Returns. Every sentence contributes useful information without redundancy, making it easy for an agent to parse.

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 simple list operation with one documented parameter, the description covers purpose, usage context, an example, and the expected return structure. Annotations cover the safety profile, so 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 coverage is 100% and the only parameter, guild_id, is already described as 'Guild to list channels for.' The example reinforces the expected format, but the description adds no significant semantic meaning beyond what the schema provides.

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 description states a specific verb and resource: 'List all channels in a Discord guild.' This clearly distinguishes it from channel-specific operations like channels_get and from thread-listing siblings such as channels_list_active_threads_guild.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit use cases: 'discover channel IDs by name; audit channel layout and forum tags.' It does not explicitly say when not to use it or name alternatives, but the context is clear enough for an agent to select it appropriately.

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

Deploy Server