Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_list_webhooks

Read-only

List webhooks in a Discord channel or entire server to inspect their IDs, names, tokens, and creators. Specify either a channel or guild ID; requires the Manage Webhooks permission.

Instructions

List the webhooks in a single channel or across a whole server (id, name, channel, token when visible, creator). Provide exactly one of channel_id or guild_id. Requires the Manage Webhooks permission. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idNoDiscord server (guild) ID (snowflake) to list all webhooks for. Mutually exclusive with channel_id.
channel_idNoID (snowflake) of a channel to list webhooks for. Mutually exclusive with guild_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
webhooksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / guild_id / pattern
      Added value: +"^\\d{17,20}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "webhooks": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "channel_id": {
+            "type": "string"
+          },
+          "creator": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "token": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "channel_id",
+          "token",
+          "creator"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "webhooks"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changedv1.6.0
    • changedInput schema / properties / channel_id / description
      Previous value: -"List webhooks for a specific channel."New value: +"ID (snowflake) of a channel to list webhooks for. Mutually exclusive with guild_id."
    • changedInput schema / properties / guild_id / description
      Previous value: -"List all webhooks in a guild."New value: +"Discord server (guild) ID (snowflake) to list all webhooks for. Mutually exclusive with channel_id."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description adds valuable behavioral context beyond that: the required Manage Webhooks permission and the 'token when visible' caveat, which warns that tokens are conditionally returned. 'Read-only' merely restates the annotation but does not contradict it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with the verb and scope front-loaded; the exclusivity rule and permission note each earn their place. The trailing 'Read-only' is redundant with the readOnlyHint annotation, a one-word waste that keeps this from a 5.

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 two-parameter list tool with an output schema, annotations, and full schema coverage, nothing material is missing: scope, returned fields, permission prerequisite, and parameter selection rule are all stated. The 'token when visible' nuance is a bonus that makes it genuinely complete.

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% — both params already document the snowflake pattern and mutual exclusivity. The description's 'exactly one of' rule restates what the schema already says, adding no new semantic information, so the baseline of 3 applies.

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 uses a specific verb ('List') with a precise resource ('webhooks') and clearly delimits the scope: a single channel or a whole server. It also summarizes the returned fields (id, name, channel, token when visible, creator), making it easy to distinguish from sibling mutation tools like discord_create_webhook, discord_edit_webhook, and discord_delete_webhook.

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?

The description gives clear invocation context: 'Provide exactly one of channel_id or guild_id' resolves the two supported modes, and 'Requires the Manage Webhooks permission' states an explicit precondition. It does not name specific alternative tools or exclusions, so it stops short of a 5.

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

Deploy Server

Other Tools