Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_webhook_with_token

Update a Discord webhook's name or avatar using its ID and token, and optionally record an audit-log reason for the change.

Instructions

Modify Webhook with Token. [PATCH /webhooks/{webhook_id}/{webhook_token}]

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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, and the description adds only the PATCH method, which is consistent but redundant with those hints. It says nothing about which fields are mutable, whether omitted fields are left untouched, that changes are recorded in the audit log via the reason field, or that the operation does not delete the webhook.

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?

Two short fragments with zero padding and the resource named up front, so there is no wasted wording. Brevity here crosses into under-specification rather than being genuinely efficient, since the endpoint line is doing work the prose should do.

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?

This is a five-parameter mutation tool with no output schema, and the description omits the two facts an agent most needs: which fields may be changed and that the webhook_token functions as the credential for the call. The annotations cover the safety profile but nothing else, leaving the definition materially incomplete.

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% and the schema already documents name, avatar, reason, webhook_id, and webhook_token individually. The description contributes nothing beyond echoing the two path parameters, so the baseline of 3 applies rather than a higher score.

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

Purpose3/5

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

The description names the verb (modify) and the resource (webhook) and adds the concrete endpoint PATCH /webhooks/{webhook_id}/{webhook_token}, which hints that authentication is via webhook token. However, it never states how this differs from the sibling modify_webhook, which is the key ambiguity an agent would face here; the sentence itself mostly restates the tool name.

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 modify_webhook, get_webhook_with_token, or delete_webhook_with_token. The only contextual cue is the HTTP path, from which the agent must infer that a webhook token rather than a bot token is required.

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