discord-mcp

discord_send_webhook_message

Send Discord messages through a webhook using only its ID and token, with optional username, avatar, and up to 10 embeds. Returns the new message ID.

Instructions

Send a message through a webhook using its ID and token (no bot permissions needed; the token authorizes the send). Supports per-message username/avatar overrides and up to 10 embeds. At least one of content or embeds is required. Returns the new message ID.

Input Schema

TableJSON Schema

Name	Required	Description
`embeds`	No	Up to 10 embed objects to attach to the webhook message.
`content`	No	Plain-text body of the message (max 2000 characters). Optional if embeds are provided.
`username`	No	Override the webhook's default display name for this message.
`avatar_url`	No	Override the webhook's default avatar for this message.
`webhook_id`	Yes	ID (snowflake) of the webhook to send through.
`webhook_token`	Yes	Secret token of the webhook (from discord_create_webhook or discord_list_webhooks).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.2.0Sep 6, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / embeds / items / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / embeds / items / properties / author / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / embeds / items / properties / fields / items / additionalProperties
```
Added value: +false
```

Changed14 schema fields changedv2.0.0Jun 27, 2026

addedInput schema / properties / avatar_url / format
```
Added value: +"uri"
```
addedInput schema / properties / avatar_url / pattern
```
Added value: +"^https?://"
```

addedInput schema / properties / embeds / items / properties / author

Added value: +{
+  "description": "Author block shown at the top of the embed.",
+  "properties": {
+    "icon_url": {
+      "description": "Small icon shown next to the author name.",
+      "format": "uri",
+      "pattern": "^https?://",
+      "type": "string"
+    },
+    "name": {
+      "description": "Author display name.",
+      "type": "string"
+    },
+    "url": {
+      "description": "URL the author name links to.",
+      "format": "uri",
+      "pattern": "^https?://",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name"
+  ],
+  "type": "object"
+}

addedInput schema / properties / embeds / items / properties / color / pattern
```
Added value: +"^#[0-9A-Fa-f]{6}$"
```

changedInput schema / properties / embeds / items / properties / fields / description

Previous value: -"Up to 25 name/value field blocks."New value: +"Up to 25 name/value field blocks. Set inline:true on a field to render it side-by-side with adjacent inline fields (up to 3 per row)."

changedInput schema / properties / embeds / items / properties / fields / items / properties / inline / description

Previous value: -"If true, render side-by-side with adjacent inline fields."New value: +"If true, render this field side-by-side with adjacent inline fields."

addedInput schema / properties / embeds / items / properties / image_url / format
```
Added value: +"uri"
```
addedInput schema / properties / embeds / items / properties / image_url / pattern
```
Added value: +"^https?://"
```
addedInput schema / properties / embeds / items / properties / thumbnail_url / format
```
Added value: +"uri"
```
addedInput schema / properties / embeds / items / properties / thumbnail_url / pattern
```
Added value: +"^https?://"
```
addedInput schema / properties / embeds / items / properties / url / format
```
Added value: +"uri"
```
addedInput schema / properties / embeds / items / properties / url / pattern
```
Added value: +"^https?://"
```
addedInput schema / properties / embeds / maxItems
```
Added value: +10
```
addedInput schema / properties / webhook_id / pattern
```
Added value: +"^\\d{17,20}$"
```

Changed18 schema fields changedv1.6.0May 28, 2026
- changedInput schema / properties / avatar_url / description
```
Previous value: -"Override the webhook's default avatar."New value: +"Override the webhook's default avatar for this message."
```
- changedInput schema / properties / content / description
```
Previous value: -"Text content of the message."New value: +"Plain-text body of the message (max 2000 characters). Optional if embeds are provided."
```
- changedInput schema / properties / embeds / description
```
Previous value: -"Optional array of embed objects."New value: +"Up to 10 embed objects to attach to the webhook message."
```
- changedInput schema / properties / embeds / items / properties / color / description
```
Previous value: -"Hex color e.g. #5865F2"New value: +"Side-bar color as a hex string, e.g. '#5865F2'."
```
- addedInput schema / properties / embeds / items / properties / description / description
```
Added value: +"Main body text of the embed (supports Markdown)."
```
- addedInput schema / properties / embeds / items / properties / fields / description
```
Added value: +"Up to 25 name/value field blocks."
```
- addedInput schema / properties / embeds / items / properties / fields / items / properties / inline / description
```
Added value: +"If true, render side-by-side with adjacent inline fields."
```
- addedInput schema / properties / embeds / items / properties / fields / items / properties / name / description
```
Added value: +"Field heading."
```
- addedInput schema / properties / embeds / items / properties / fields / items / properties / value / description
```
Added value: +"Field body text."
```
- addedInput schema / properties / embeds / items / properties / footer / description
```
Added value: +"Footer text shown at the bottom of the embed."
```
- addedInput schema / properties / embeds / items / properties / image_url / description
```
Added value: +"Large image shown below the embed body."
```
- addedInput schema / properties / embeds / items / properties / thumbnail_url / description
```
Added value: +"Small image shown in the top-right corner."
```
- addedInput schema / properties / embeds / items / properties / timestamp / description
```
Added value: +"If true, stamp the embed with the current time."
```
- addedInput schema / properties / embeds / items / properties / title / description
```
Added value: +"Embed title shown in bold at the top."
```
- addedInput schema / properties / embeds / items / properties / url / description
```
Added value: +"URL that makes the title clickable."
```
- changedInput schema / properties / username / description
```
Previous value: -"Override the webhook's default username."New value: +"Override the webhook's default display name for this message."
```
- addedInput schema / properties / webhook_id / description
```
Added value: +"ID (snowflake) of the webhook to send through."
```
- addedInput schema / properties / webhook_token / description
```
Added value: +"Secret token of the webhook (from discord_create_webhook or discord_list_webhooks)."
```
Addedv1.5.0May 8, 2026
Removedv1.0.0May 1, 2026
First observedv0.1.0Mar 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description adds useful behavioral context beyond the annotations: the token authorizes the send, no bot permissions are needed, content or embeds are required, and the message ID is returned. This meaningfully explains the operation's side effects and return value without contradicting the annotations.

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 and front-loaded: core action first, then feature highlights, then a critical validation rule, then the return value. Every sentence adds value and there is no redundant or vague wording.

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?

Given the rich 100%-covered input schema and no output schema, the description provides the missing pieces: auth requirements, payload constraints, and return value. An agent has enough information to invoke this tool correctly and understand what to expect.

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?

Schema coverage is 100%, so the baseline is 3. The description adds the important cross-parameter constraint that at least one of content or embeds is required, which is not enforced by the schema's required fields. It also summarizes the username/avatar overrides and 10-embed limit, though those are already in the schema.

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?

Description states the specific action: send a message through a webhook using its ID and token, with no bot permissions needed. This clearly differentiates it from bot-token message tools like discord_send_message and from webhook management tools like discord_edit_webhook. The resource and mechanism are unambiguous.

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 context for when to use this tool: when you have a webhook ID and token and do not need bot permissions. It does not explicitly name alternative tools or state when not to use it, but the auth distinction makes the intended usage fairly evident.

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

Deploy Server

discord_send_webhook_message

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools