Webhook Tools

Webhook lifecycle operations.

Webhook tools can expose cross-channel or cross-guild behavior if they are not constrained carefully. Prefer explicit X-Target-Guilds and X-Target-Channels headers when using them in user-driven flows.

create_webhook #

• Purpose: create a channel webhook.
• Key arguments: channel scope, name.
• Optional fields: avatar, reason.
• Response shape:
• returns a usable webhook url
• returns token on creation so the new webhook can be used immediately

list_channel_webhooks #

• Purpose: list webhooks for one channel.
• Key arguments: channel scope.
• Response shape:
• includes url
• does not return token

list_guild_webhooks #

• Purpose: list webhooks for one guild.
• Key arguments: guild_id or guild_name.
• Response shape:
• includes url
• does not return token

get_webhook #

• Purpose: fetch one webhook.
• Key arguments: webhook_id.
• Notes:
• The Discord MCP resolves webhook metadata before applying some target checks.
• Response shape:
• keeps url visible
• keeps token only when the webhook belongs to the current bot
• otherwise returns a masked token

edit_webhook #

• Purpose: edit webhook attributes.
• Key arguments: webhook_id.
• Optional fields: name, avatar, channel_id or channel_name.
• Response shape:
• keeps url visible
• does not return token

delete_webhook #

• Purpose: delete a webhook.
• Key arguments: webhook_id.