MCP-Discord

discord_send_webhook_message

Send messages to a Discord channel using a webhook. Configure webhook details, content, username, avatar, and thread ID for precise message delivery.

Instructions

Sends a message to a Discord channel using a webhook

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "webhookId": "<webhookId>",
      "webhookToken": "<webhookToken>",
      "content": "<content>"
    },
    "name": "discord_send_webhook_message"
  }
}

Input Schema

Name	Required	Description	Default
`content`	Yes
`threadId`	No
`username`	No
`avatarURL`	No
`webhookId`	Yes
`webhookToken`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2025

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It states the primary effect (sending a message) but gives no additional context about side effects, required permissions, error behavior, or irreversibility, which are relevant for a create-type action.

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 a single concise sentence that immediately conveys the tool's purpose. Every word contributes, and it is not bloated or repetitive.

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

Completeness2/5

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

For a tool with six parameters and no output schema or annotations, this description is too thin. It omits guidance on optional parameters, return behavior, failure cases, and validation, which are necessary for an agent to use the tool confidently in varied contexts.

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

Parameters2/5

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

With 0% schema description coverage, the description must compensate, but it only weakly maps 'message' to content and 'webhook' to webhookId/webhookToken. It provides no explanation for threadId, username, or avatarURL, leaving their purpose unclear.

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 starts with a specific verb 'Sends' and clearly identifies the resource as 'a message to a Discord channel'. The qualifier 'using a webhook' differentiates it from sibling tools like discord_send, which likely sends via a bot session, and discord_send_voice, which handles voice.

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?

Usage is implied by 'using a webhook', suggesting it should be used when webhook credentials are available. However, it does not explicitly state when to prefer this over alternatives such as discord_send, nor does it mention prerequisites or exclusions.

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

Deploy Server