discord-mcp

webhooks_modify_with_token

Idempotent

Modify a webhook's name and avatar with its token, no bot auth required. Use this when you hold the token but lack guild access.

Instructions

Purpose: Update a webhook (name + avatar only) using its token, no bot auth.

When to use:

You hold the token but lack guild access.

Restrictions:

Cannot move the webhook (channel_id not accepted on this route - use webhooks_modify).
Discord does not record audit reasons on token-auth routes, so audit_reason is intentionally absent.

Auth: NO Authorization: Bot … header.

Returns: Updated webhook record. name remains raw creator-controlled data; untrusted_name provides a separately fenced copy.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New display name
`token`	Yes	Webhook secret - treat as credential, do not log
`avatar`	No	base64-encoded image data URI, or null to clear
`webhook_id`	Yes	Webhook to modify

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.28.0Sep 15, 2026

removedInput schema / properties / avatar / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / avatar / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "application_id": {
-        "anyOf": [
-          {
-            "description": "Discord application ID",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "avatar": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "channel_id": {
-        "anyOf": [
-          {
-            "description": "Discord channel ID (snowflake)",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "description": "Discord webhook ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "type": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "untrusted_name": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "type",
-      "channel_id",
-      "application_id",
-      "name",
-      "avatar",
-      "untrusted_name"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "application_id": {
+        "anyOf": [
+          {
+            "description": "Discord application ID",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "avatar": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "channel_id": {
+        "anyOf": [
+          {
+            "description": "Discord channel ID (snowflake)",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "id": {
+        "description": "Discord webhook ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "type": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "untrusted_name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "channel_id",
+      "application_id",
+      "name",
+      "avatar",
+      "untrusted_name"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already indicate mutation (readOnlyHint=false), idempotence, and non-destructiveness. The description adds valuable behavioral context beyond annotations: no Authorization: Bot header is sent, audit_reason is intentionally absent on token-auth routes, and the return has untrusted_name as a separately fenced copy. This significantly helps an agent understand the operational implications of calling this tool.

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

Conciseness5/5

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

The description is tightly organized with bolded section headers and zero filler. The purpose is front-loaded, followed by when-to-use, restrictions, auth, and returns. Every sentence conveys essential information, making it efficient and easy to scan.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with an output schema and capable annotations, the description covers all necessary operational context: auth mode, restrictions, audit behavior, and return semantics. Nothing an agent needs to safely invoke it is missing.

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%, and each parameter already has a clear description (e.g., 'Webhook secret - treat as credential, do not log'). The description adds scope-level clarity ('name + avatar only') but does not add per-parameter detail beyond the schema. This meets the baseline for full schema coverage.

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 purpose statement is specific: 'Update a webhook (name + avatar only) using its token, no bot auth.' It names the exact verb, resource, and scope of changes, and distinguishes this from the sibling webhooks_modify by noting it cannot move the webhook. This makes it immediately clear what the tool does and how it differs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'When to use' section explicitly states the condition: 'You hold the token but lack guild access.' It also names the alternative tool for the unsupported use case: 'use webhooks_modify' for moving the webhook. This provides clear, actionable routing guidance with no ambiguity.

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

Deploy Server