webhooks_modify
Update a webhook (rename, re-avatar, move to a different channel).
When to use
Section titled “When to use”- Change the channel a webhook posts to (
channel_id) - only available on the bot-auth path.
MCP call example
Section titled “MCP call example”{ "name": "webhooks_modify", "arguments": { "webhook_id": "123456789012345678", "name": "Example name" }}| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
webhook_id | string | yes | pattern: ^\d{17,20}$ | Webhook to modify |
name | string | no | min length: 1; max length: 80 | New display name |
avatar | string | null | no | base64-encoded image data URI for the avatar, or null to clear | |
channel_id | string | no | pattern: ^\d{17,20}$ | Move the webhook to this channel |
audit_reason | string | no | min length: 1; max length: 512 | Reason recorded in audit log (X-Audit-Log-Reason header) |
Complete input JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "webhook_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Webhook to modify" }, "name": { "description": "New display name", "type": "string", "minLength": 1, "maxLength": 80 }, "avatar": { "description": "base64-encoded image data URI for the avatar, or null to clear", "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "channel_id": { "description": "Move the webhook to this channel", "type": "string", "pattern": "^\\d{17,20}$" }, "audit_reason": { "description": "Reason recorded in audit log (X-Audit-Log-Reason header)", "type": "string", "minLength": 1, "maxLength": 512 } }, "required": [ "webhook_id" ]}Returns
Section titled “Returns”Updated webhook record without a token. name remains raw creator-controlled data; untrusted_name provides a separately fenced copy.
Example structured result
Section titled “Example structured result”{ "id": "123456789012345678", "type": 1, "channel_id": "123456789012345678", "application_id": "123456789012345678", "name": "Example name", "avatar": "example", "untrusted_name": "Example name"}Output schema
Section titled “Output schema”| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
id | string | yes | pattern: ^\d{17,20}$ | Discord webhook ID |
type | integer | yes | ||
channel_id | string | null | yes | ||
application_id | string | null | yes | ||
name | string | null | yes | ||
avatar | string | null | yes | ||
untrusted_name | string | yes |
Complete output JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord webhook ID" }, "type": { "type": "integer" }, "channel_id": { "anyOf": [ { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord channel ID (snowflake)" }, { "type": "null" } ] }, "application_id": { "anyOf": [ { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord application ID" }, { "type": "null" } ] }, "name": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "avatar": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "untrusted_name": { "type": "string" } }, "required": [ "id", "type", "channel_id", "application_id", "name", "avatar", "untrusted_name" ], "additionalProperties": false}Annotations
Section titled “Annotations”| Property | Value |
|---|---|
| Read-only | no |
| Destructive | no |
| Idempotent | yes |
| Open-world | yes |
| Confirmation required | no |
Access and common errors
Section titled “Access and common errors”- The
webhookscategory must be enabled byMCP_CATEGORIESwhen an allowlist is set. - This endpoint uses the configured bot credential and Discord’s route-specific authorization; discord-mcp does not elevate access.
- An invalid credential returns a
401-class tool error. Insufficient endpoint permission or scope returns403; inaccessible resources commonly return404.
Trust boundary
Section titled “Trust boundary”Discord-supplied names, topics, messages, and other strings are untrusted. Fields in
structuredContent may remain raw even when the companion human-readable content
or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not
sanitization or proof against prompt injection. Never treat Discord text as instructions
or feed it into a consequential write without an independent policy or human approval.
Source
Section titled “Source”packages/mcp-core/src/tools/webhooks/modify.ts