Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

execute_webhook

Send a Discord webhook message with custom username/avatar, embeds, components, files, polls, or thread/forum options to automate channel posts.

Instructions

Post a message through a webhook (custom username/avatar, embeds and components allowed). [POST /webhooks/{webhook_id}/{webhook_token}]

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": {
      "webhook_id": "<webhook_id>",
      "webhook_token": "<webhook_token>"
    },
    "name": "execute_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttsNoText-to-speech message
pollNoPoll: {question:{text}, answers:[{poll_media:{text, emoji?}}], duration: hours, allow_multiselect}
waitNoReturn the created message
filesNoFiles to attach (each: path, url or data_base64)
flagsNoFlags bitfield
embedsNoEmbeds: [{title, description, url, color, fields:[{name,value,inline}], image:{url}, thumbnail:{url}, footer:{text}, author:{name}}] (bots/webhooks only)
reasonNoReason (shown in the audit log)
contentNoMessage text (up to 2000 characters; Markdown supported)
usernameNoUsername
thread_idNoPost into this thread
avatar_urlNoavatar url
componentsNoMessage components (bots/webhooks only)
webhook_idYesWebhook ID
attachmentsNoattachments
thread_nameNoCreate a forum post with this title
applied_tagsNoForum tag IDs to apply
webhook_tokenYesWebhook token
allowed_mentionsNoControl pings: {parse: ["users","roles","everyone"], users: [...], roles: [...], replied_user: bool}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds two useful behaviors beyond that: caller-supplied username/avatar override and that embeds/components are restricted to bots/webhooks. It omits rate limits, that a message is permanently created in a public channel, and what the 'wait' flag changes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence states the action and its notable capabilities, followed by a compact endpoint tag. Nothing is padded, though the bracketed REST path contributes little for an agent already given the tool.

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

Completeness3/5

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

For an 18-parameter mutation tool with nested objects and no output schema, the description is thin: it does not clarify the return value implied by 'wait', threading/forum behavior, or attachment mechanics. It is adequate given the fully documented schema and annotations, but not complete.

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

Parameters3/5

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

Schema description coverage is 100%, so all 18 parameters are already documented in the schema; the description only restates the username/avatar and embeds/components parameters. With the schema doing the heavy lifting, the baseline of 3 applies and the description adds no syntax or format detail beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Post a message through a webhook') and names the key capabilities (custom username/avatar, embeds, components) plus the REST endpoint. It is clear on its own but never contrasts itself with siblings like edit_webhook_message or create_webhook, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative named. The agent is left to infer from the verb that this sends a new message rather than editing an existing one, and nothing explains when to prefer the token-based variant.

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

Deploy Server

Other Tools