discord-mcp

discord_fetch_webhook_message

Read-only

Fetch a single Discord webhook message by its ID using the webhook ID and token. Retrieve message details like content, embed count, and timestamp.

Instructions

Fetch a single message sent through a webhook (id, content, embed count, timestamp), using the webhook's ID and token. Read-only. Requires the original 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>",
      "message_id": "<message_id>"
    },
    "name": "discord_fetch_webhook_message"
  }
}

Input Schema

Name	Required	Description
`message_id`	Yes	ID of the webhook message to fetch.
`webhook_id`	Yes	ID (snowflake) of the webhook that sent the message.
`webhook_token`	Yes	Secret token of the webhook.

Output Schema

Name	Required	Description	Default
`id`	Yes
`embeds`	Yes
`content`	Yes
`timestamp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.0Sep 6, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed3 schema fields changedv2.0.0Jun 27, 2026

addedInput schema / properties / message_id / pattern
```
Added value: +"^\\d{17,20}$"
```
addedInput schema / properties / webhook_id / pattern
```
Added value: +"^\\d{17,20}$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "content": {
+      "type": "string"
+    },
+    "embeds": {
+      "type": "number"
+    },
+    "id": {
+      "type": "string"
+    },
+    "timestamp": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "content",
+    "embeds",
+    "timestamp"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedv1.6.0May 28, 2026
- addedInput schema / properties / message_id / description
```
Added value: +"ID of the webhook message to fetch."
```
- addedInput schema / properties / webhook_id / description
```
Added value: +"ID (snowflake) of the webhook that sent the message."
```
- addedInput schema / properties / webhook_token / description
```
Added value: +"Secret token of the webhook."
```
Addedv1.5.0May 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description reinforces read-only behavior while adding valuable context: the requirement of the original webhook token and a summary of returned data (id, content, embed count, timestamp). No contradiction with annotations.

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?

A single sentence delivers the operation, resource scope, return summary, read-only nature, and auth requirement with zero filler. Information is front-loaded 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 simple single-message fetch with 3 fully documented required parameters, an output schema, and safety annotations, the description covers the critical token prerequisite and operation scope. Nothing essential is missing for an agent to invoke it correctly.

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%, so the individual parameter descriptions already handle semantics. The tool description adds only the nuance that the token must be the 'original' webhook token, which is a minor enhancement over the schema.

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?

Clearly identifies the verb ('Fetch'), the resource ('a single message sent through a webhook'), and the scope ('using the webhook's ID and token'). The parenthetical return fields and the webhook-specific framing distinguish it from sibling tools like discord_read_messages or discord_get_message_attachments.

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

Usage Guidelines4/5

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

States the key prerequisite 'Requires the original webhook token,' which is the primary condition for using this tool. It implicitly differentiates from non-webhook message tools, but does not explicitly name alternatives or when-not-to-use scenarios.

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

Deploy Server