Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update webhook

update_webhook

Rename a Discord webhook, change its avatar, or move it to another channel to keep notifications accurate and organized.

Instructions

Rename a webhook, change its avatar, or move it to another 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": {
      "webhook": "<webhook>"
    },
    "name": "update_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
guildNoGuild (server) name or ID. Omit to use the default guild.
channelNoMove the webhook to this channel.
webhookYesWebhook name or ID.
avatar_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds only a field list; it does not disclose partial-update semantics, whether changes are reversible, permission requirements, or that the webhook must already exist — all traits annotations do not cover.

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 listing the three mutating actions with no filler. It is efficiently sized, though the list-based phrasing leaves behavior implicit rather than stating it outright.

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 five-parameter mutation tool with no output schema, the definition should say what happens to unspecified fields and that 'webhook' is required. As written, an agent could call it without knowing the identifier requirement or the partial-update contract.

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 coverage is 60%, so the schema already documents guild and channel. The description correctly maps 'avatar' to avatar_url and 'name' to name, adding marginal meaning, but it never mentions the required 'webhook' identifier, which is the one parameter an agent must supply.

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?

Uses a specific verb ('Rename', 'change', 'move') with the resource 'webhook' and enumerates the editable attributes, which distinguishes it from create_webhook/delete_webhook. It stops short of naming alternatives, but the intent and scope are 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?

There is no guidance on when to choose this tool over siblings such as update_channel, nor any statement that it is the only way to modify an existing webhook. Nothing is said about prerequisites, permissions, or whether omitted fields are preserved.

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