discord-mcp

webhooks_list_channel

Read-onlyIdempotent

List all webhooks on a Discord channel to audit for unauthorized entries or identify targets before sending messages.

Instructions

Purpose: List webhooks attached to a single channel.

When to use: discover webhooks before sending via webhooks_execute; audit a channel for unauthorized webhooks.

Returns: {webhooks:[{id,name,type,channel_id,application_id}], count}. Structured names remain raw creator-controlled data; the human-readable text response fences them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channel_id`	Yes	Channel to query

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": {
-      "count": {
-        "type": "number"
-      },
-      "webhooks": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "application_id": {
-              "anyOf": [
-                {
-                  "description": "Discord application ID",
-                  "pattern": "^\\d{17,20}$",
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "channel_id": {
-              "anyOf": [
-                {
-                  "description": "Discord channel ID (snowflake)",
-                  "pattern": "^\\d{17,20}$",
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "id": {
-              "description": "Discord webhook ID",
-              "pattern": "^\\d{17,20}$",
-              "type": "string"
-            },
-            "name": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "type": {
-              "maximum": 9007199254740991,
-              "minimum": -9007199254740991,
-              "type": "integer"
-            }
-          },
-          "required": [
-            "id",
-            "name",
-            "type",
-            "channel_id",
-            "application_id"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "webhooks",
-      "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": {
+      "count": {
+        "type": "number"
+      },
+      "webhooks": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "application_id": {
+              "anyOf": [
+                {
+                  "description": "Discord application ID",
+                  "pattern": "^\\d{17,20}$",
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "channel_id": {
+              "anyOf": [
+                {
+                  "description": "Discord channel ID (snowflake)",
+                  "pattern": "^\\d{17,20}$",
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "id": {
+              "description": "Discord webhook ID",
+              "pattern": "^\\d{17,20}$",
+              "type": "string"
+            },
+            "name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "type",
+            "channel_id",
+            "application_id"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "webhooks",
+      "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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds value by specifying the exact return structure ({webhooks:[{id,name,type,channel_id,application_id}], count}) and a behavioral note about structured names being raw creator-controlled data with text fencing. This goes beyond the annotations and gives the agent useful context about output handling. No contradiction exists.

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 compact and well-structured with clear headings (Purpose, When to use, Returns). The most important information (purpose) is front-loaded, and every sentence earns its place. There is no redundancy or filler, making it easy for an agent to parse quickly.

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 tool with one parameter and an output schema, the description provides sufficient context: it states what it does, when to use it, and what it returns. The output schema already documents the return fields in detail, so the description need not repeat them. The note about structured names adds a behavioral nuance. Nothing essential is missing for correct invocation.

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% – the only parameter (channel_id) is fully described as 'Channel to query'. The description adds no additional information about the parameter format, constraints, or usage beyond what the schema provides. Since the schema fully covers the parameter, the baseline score of 3 applies, and the description does not need to compensate.

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 ('List'), a specific resource ('webhooks'), and a clear scope ('attached to a single channel'). This clearly distinguishes it from the sibling webhooks_list_guild, which lists webhooks at the guild level. The purpose is unambiguous and immediately actionable.

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?

Provides explicit when-to-use guidance: 'discover webhooks before sending via webhooks_execute' and 'audit a channel for unauthorized webhooks'. It also references a specific sibling tool (webhooks_execute) for context. Although it doesn't explicitly state when not to use it, the 'single channel' scope implicitly contrasts with webhooks_list_guild, and the use cases are concrete enough for an agent to select it correctly.

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

Deploy Server