Skip to main content
Glama
kongyo2

Discord Webhook MCP

Edit Discord Message

discord_edit_message
Idempotent

Edit a Discord message sent via webhook by specifying its message ID. Update the content, embeds, or both while respecting rate limits.

Instructions

Webhookで送信したメッセージを編集します。

content、embedsのいずれか最低1つが必要です。 環境変数DISCORD_WEBHOOK_URLに設定されたWebhookを使用します。

⚠️ レート制限: 30リクエスト/分/チャンネル

Args:

  • message_id (string, required): 編集するメッセージID

  • content (string, optional): 新しいメッセージ内容(1-2000文字)

  • embeds (array, optional): 新しいEmbedの配列(最大10個、合計6000文字以内)

  • allowed_mentions (object, optional): 許可されたメンション設定

Returns: { "success": boolean, // 編集が成功したか "message_id": string, // 編集されたメッセージのID "timestamp": string // 編集日時 (ISO 8601形式) }

Examples:

  • テキストを編集: { "message_id": "123456789", "content": "更新後のメッセージ" }

  • Embedを編集: { "message_id": "123456789", "embeds": [{ "title": "新しいタイトル", "color": 0xFF0000 }] }

Error Handling:

  • "Validation error: content/embeds - content、embeds のうち最低1つを指定してください"

  • "Discord Webhook error: 404 Not Found - Message not found"

  • "Discord Webhook error: 400 Bad Request - Invalid message ID"

  • "Discord Webhook error: レート制限に達しました" - 429エラー時、retry-after秒後に再試行

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
message_idYes編集するメッセージID
contentNo新しいメッセージ内容 (最大2000文字)
embedsNo新しいEmbedの配列 (最大10個)
allowed_mentionsNo許可されたメンション設定
Behavior4/5

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

The description adds rate limit (30 req/min/channel) and error handling details beyond the annotations. It does not contradict annotations, though openWorldHint=true might imply side effects not fully explained.

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 well-structured with sections (requirements, examples, errors) and uses bullet points. It is concise yet comprehensive, with no wasted words.

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?

Despite no output schema, the description provides a clear return structure, error handling examples, and rate limit details. It covers all necessary aspects for an agent to use the tool correctly.

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%, but the description adds the requirement of at least one of content/embeds and provides examples. It adds value beyond the schema, hence above baseline.

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 clearly states the tool edits messages sent via webhook. It distinguishes from sibling tools (delete, send) by focusing on editing existing messages.

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?

The description specifies that at least one of content or embeds is required and mentions the webhook URL environment variable. However, it does not explicitly contrast with siblings or state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kongyo2/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server