Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

edit_webhook_message

Updates an existing Discord webhook message using its webhook and message IDs, allowing changes to content, embeds, files, components, flags, or allowed mentions.

Instructions

Edit Webhook Message. [PATCH /webhooks/{webhook_id}/{webhook_token}/messages/{message_id}]

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>",
      "message_id": "<message_id>"
    },
    "name": "edit_webhook_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttsNoText-to-speech 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)
componentsNoMessage components (bots/webhooks only)
message_idYesMessage ID
webhook_idYesWebhook ID
attachmentsNoattachments
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

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds only the HTTP verb and route, which hint at mutation and token-based auth but add essentially no context about reversibility, whether omitted fields are cleared or preserved, or edit-window limits. For a mutation tool with 12 parameters this is thin.

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

Conciseness3/5

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

The description is very short and front-loaded with no filler, but its brevity reflects under-specification rather than disciplined concision. A verbatim name plus a raw endpoint path is compact yet conveys little an agent can act on.

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?

With 12 parameters, nested objects, a mutation semantics, and no output schema, the definition should explain at minimum which fields can be edited and what happens to unspecified ones. Instead it offers only the route, leaving the agent to rely entirely on schema property descriptions and sibling-name inference.

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 every parameter, including nested file and embed fields, is already documented in the schema. The description adds no semantics beyond that, so the baseline of 3 applies.

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

Purpose2/5

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

The description restates the tool name ('Edit Webhook Message') and appends the raw HTTP route '[PATCH /webhooks/{webhook_id}/{webhook_token}/messages/{message_id}]'. The route does convey that this edits a message owned by a webhook rather than a bot/user, but it never states that in prose, and it does nothing to distinguish the tool from the sibling edit_message beyond the implied resource. This is close to tautology with a path string attached.

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 when-to-use guidance, no mention of prerequisites (webhook token ownership), and no reference to alternatives such as edit_message or edit_my_message. The agent must infer from the name alone that this is for webhook-authored messages, and must infer that it should not be used for regular messages.

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