Discord MCP Extended

discord_edit_webhook

Update a Discord webhook's name, avatar, or target channel to keep notifications accurate and current.

Instructions

Edits an existing webhook for a Discord channel

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

Input Schema

Name	Required	Description	Default
`name`	No
`avatar`	No
`reason`	No
`channelId`	No
`webhookId`	Yes
`webhookToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.4Aug 9, 2026

TDQS

C2.5/5.0

Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits but does not. It merely states 'Edits an existing webhook' with no mention of side effects, required permissions, reversibility, or what happens to the webhook configuration. This is a significant transparency gap for a mutation tool.

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?

The description is a single, front-loaded sentence with no wasted words. It is concise and grammatically clear, but the lack of any additional structure (e.g., parameter hints) makes it less helpful than its brevity might suggest.

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

Completeness1/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, no annotations, and no output schema, the description provides almost no context. It does not explain return values, error conditions, or parameter relationships, making it inadequate for an agent to invoke the tool correctly in diverse contexts.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention any of the six parameters (name, avatar, reason, channelId, webhookToken). The agent receives no semantic context for the parameters beyond their names, which is insufficient for correct invocation.

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 uses the specific verb 'Edits' and clearly identifies the resource as 'an existing webhook for a Discord channel.' This distinguishes it from sibling tools like discord_create_webhook and discord_delete_webhook, making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives such as discord_create_webhook or discord_send_webhook_message. It does not mention prerequisites, typical use cases, or exclude scenarios, leaving the agent without decision support.

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