discord-mcp

webhooks_modify

Idempotent

Update a Discord webhook's name, avatar, or target channel. Provide the webhook ID and new values to change how it appears or where it posts.

Instructions

Purpose: Update a webhook (rename, re-avatar, move to a different channel).

When to use:

Change the channel a webhook posts to (channel_id) - only available on the bot-auth path.

Returns: Updated webhook record without a token. name remains raw creator-controlled data; untrusted_name provides a separately fenced copy.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New display name
`avatar`	No	base64-encoded image data URI for the avatar, or null to clear
`channel_id`	No	Move the webhook to this channel
`webhook_id`	Yes	Webhook to modify
`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"
-          }
-        ]
-      },
-      "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"
+        ]
+      },
+      "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.2/5.0

Behavior4/5

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

Annotations already indicate this is a mutating, idempotent, non-destructive operation. The description adds useful behavioral context beyond that: the updated record is returned without a token, and name is raw creator-controlled data while untrusted_name is fenced separately. The bot-auth limitation for channel_id is also valuable behavioral transparency.

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, well-structured with clear labeled sections, and front-loads the primary purpose. Every sentence contributes either to what the tool does, when to use a special feature, or what the caller should expect in the response. There is no repetition of the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the fully described schema, existing output schema, and annotations, the description covers the important behavioral details: the bot-auth-only channel_id path, the tokenless return record, and the name/untrusted_name distinction. A fuller note about when to use webhooks_modify_with_token instead would make it fully complete, but the current context is sufficient for correct use in most cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% description coverage, so the baseline is 3. The description adds meaningful extra semantics on top: channel_id is only available on the bot-auth path, and name is treated as raw creator-controlled data with a separately fenced untrusted_name counterpart. These enrich the parameter meaning beyond the schema's straightforward field descriptions.

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 purpose is explicit and specific: 'Update a webhook (rename, re-avatar, move to a different channel).' This clearly names the verb and resource, enumerates the concrete operations, and stands apart from sibling webhook tools like webhooks_get, webhooks_create, and webhooks_delete. The addition of the bot-auth limitation further helps distinguish this from the token-based modify variant.

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

Usage Guidelines3/5

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

The description provides one specific usage condition: channel moves via channel_id are only available on the bot-auth path. However, it does not explicitly tell the agent when to prefer this tool over webhooks_modify_with_token, nor when not to use it for rename or avatar changes. Guidance is partial rather than complete.

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

Deploy Server