discord-mcp

webhooks_create

Create a Discord webhook in a channel to automate notifications, alerts, or cross-posting. Returns the webhook token required to send messages.

Instructions

Purpose: Create a new webhook attached to a channel.

When to use:

Provision an automation endpoint (CI notifier, alert relay, cross-poster).

When NOT to use:

Sending one-off bot messages → messages_send.

Returns: Full webhook record INCLUDING the token - store it as a secret. The agent needs the token to call webhooks_execute. name remains raw creator-controlled data; untrusted_name provides a separately fenced copy.

Note: This is the only webhooks_*_get-style tool that exposes token in its response. webhooks_get projects token OUT.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Webhook display name (max 80 chars)
`avatar`	No	base64-encoded image data URI for the webhook avatar, or null
`channel_id`	Yes	Channel that will host the webhook
`audit_reason`	No	Reason recorded in audit log (X-Audit-Log-Reason header)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.28.0Sep 15, 2026

removedInput schema / properties / avatar / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / avatar / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "application_id": {
-        "anyOf": [
-          {
-            "description": "Discord application ID",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "avatar": {
-        "anyOf": [
-          {
-            "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"
-          }
-        ]
-      },
-      "token": {
-        "description": "Discord webhook token (secret - treat as credential, do not log)",
-        "maxLength": 100,
-        "minLength": 60,
-        "type": "string"
-      },
-      "type": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "untrusted_name": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "type",
-      "channel_id",
-      "application_id",
-      "name",
-      "avatar",
-      "untrusted_name"
-    ],
-    "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": {
+      "application_id": {
+        "anyOf": [
+          {
+            "description": "Discord application ID",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "avatar": {
+        "type": [
+          "string",
+          "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"
+        ]
+      },
+      "token": {
+        "description": "Discord webhook token (secret - treat as credential, do not log)",
+        "maxLength": 100,
+        "minLength": 60,
+        "type": "string"
+      },
+      "type": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "untrusted_name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "channel_id",
+      "application_id",
+      "name",
+      "avatar",
+      "untrusted_name"
+    ],
+    "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.7/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing that the response includes the token, instructing the agent to store it as a secret, and explaining that the token is needed for webhooks_execute. It also adds useful trust context about `name` being raw creator-controlled data and `untrusted_name` being a fenced copy. This is critical behavioral and security-relevant information that annotations do not convey.

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 clear headings, bullet points, and front-loaded purpose. Every sentence adds value: purpose, usage, exclusions, return-value security, and cross-tool differentiation. It is thorough without being bloated.

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 create operation with an existing output schema and full parameter documentation, the description covers all essential context: what the tool does, when to use it, what it returns, and how the return value should be handled. The security warning about the token is especially important for correct and safe agent behavior.

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 parameters are already fully documented. The description adds no additional input parameter semantics beyond what the schema provides. Baseline 3 is appropriate because the schema carries the semantic load for name, avatar, channel_id, and audit_reason.

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: 'Create a new webhook attached to a channel.' It clearly identifies the tool's core function and is easily distinguished from sibling webhook tools like webhooks_get, webhooks_modify, and webhooks_execute. The purpose is unambiguous and action-oriented.

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?

Explicit when-to-use guidance is provided with concrete use cases like CI notifier, alert relay, and cross-poster. It also names a specific alternative (messages_send) for the 'when NOT to use' case, helping the agent route correctly without opening other tool schemas.

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

Deploy Server