discord-mcp

webhooks_get_with_token

Read-onlyIdempotent

Retrieve a Discord webhook using its ID and token without bot authentication. Works when you have the token but lack guild access.

Instructions

Purpose: Get a webhook by id + token without bot auth.

When to use:

You hold the token (e.g. from webhooks_create) but lack guild access.

Auth: Sends NO Authorization: Bot … header - Discord rejects bot auth on token routes.

Returns: Webhook record. token is preserved here (the caller already has it). name remains raw creator-controlled data; untrusted_name provides a separately fenced copy.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`token`	Yes	Webhook secret - treat as credential, do not log
`webhook_id`	Yes	Webhook to fetch

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

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"
-          }
-        ]
-      },
-      "token": {
-        "description": "Discord webhook token (secret - treat as credential, do not log)",
-        "maxLength": 100,
-        "minLength": 60,
-        "type": "string"
-      },
-      "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"
+        ]
+      },
+      "token": {
+        "description": "Discord webhook token (secret - treat as credential, do not log)",
+        "maxLength": 100,
+        "minLength": 60,
+        "type": "string"
+      },
+      "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.9/5.0

Behavior5/5

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

Annotations already mark readOnlyHint, idempotentHint, and destructiveHint, but the description adds behavioral detail beyond that: it states that no Authorization: Bot header is sent and explains the consequence ('Discord rejects bot auth on token routes'). It also discloses data handling nuances (token preserved, untrusted_name provides fenced copy), adding real value.

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 well-structured with bold headers (Purpose, When to use, Auth, Returns) and is concise. Every section adds value without redundancy. It is front-loaded with the core purpose and then gives targeted guidance.

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?

Given an output schema exists, the description doesn't need to detail return values fully, but it does highlight key output nuances. It covers the purpose, when to use, auth specifics, and important return-field semantics. For a two-parameter tool, this is complete and an agent can call it correctly without ambiguity.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds extra meaning by explaining that the token is preserved in the response (caller already has it) and that 'name' is raw creator-controlled data while 'untrusted_name' is a fenced copy. This clarifies the output semantics related to the parameters, but doesn't add much about how to construct the parameters themselves beyond the schema. Thus a 4, not 5.

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 states a specific verb and resource ('Get a webhook by id + token') and immediately distinguishes it from the bot-auth variant by adding 'without bot auth.' This clearly differentiates it from sibling webhooks_get, which presumably uses bot auth, and from webhooks_get_with_token's token variant.

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?

It explicitly gives a condition: 'You hold the token (e.g. from webhooks_create) but lack guild access.' This tells when to use this tool and implicitly when not to (when you have guild access, use the bot-auth version). It also explains the auth requirement and that Discord rejects bot auth on token routes, which is critical context.

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

Deploy Server