Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_webhook

Update a Discord webhook's name, avatar, or channel via PATCH to keep integrations pointed at the right destination.

Instructions

Modify Webhook. [PATCH /webhooks/{webhook_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>"
    },
    "name": "modify_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName
avatarNo
reasonNoReason (shown in the audit log)
channel_idNoChannel ID
webhook_idYesWebhook ID

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 covered. The only real addition from the description is the PATCH verb and route, which implies a partial update rather than a full replacement, but nothing is said about what the caller must own, what happens to omitted fields, or what is returned.

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?

It is short and front-loaded, but the first sentence merely repeats the tool name and the second is a bare route fragment, so the two units of text carry very little information. It is compact without being informative, which is under-specification rather than genuine conciseness.

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?

A 5-parameter mutation tool with no output schema and only partial schema coverage needs the description to explain the edit semantics and preconditions; instead it supplies only a name and an HTTP route. An agent could invoke it correctly by guessing from parameter names, but the definition does not carry its weight.

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 80%, so the schema already documents name, avatar, reason, channel_id, and webhook_id. The description adds nothing on top of that, and notably the interaction between name and webhook_id (only webhook_id is required) is not explained. Baseline 3 applies when the schema carries the semantics.

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 is 'Modify Webhook. [PATCH /webhooks/{webhook_id}]', which essentially restates the tool name plus an HTTP route. It does distinguish the resource and the ID-based addressing, but it offers no statement of what aspects of a webhook are being modified or how this differs from siblings like modify_webhook_with_token.

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 (e.g., whether a bot token or webhook token is needed), no exclusions, and no pointer to the token-based sibling. The bracketed endpoint hints at the authentication context but does not instruct the agent.

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