discord-mcp

messages_get

Read-onlyIdempotent

Retrieve a single Discord message by its unique ID using the channel ID and message ID. Use this to inspect a specific message's current content, verify its existence, or read its details before editing.

Instructions

Purpose: Fetch a single Discord message by ID.

When to use:

Inspect a specific message referenced by another tool or by the user.
Verify message exists / read its current content before editing.

When NOT to use:

Reading a window of recent messages → use messages_read.

Example: {channel_id:"112233445566778899", message_id:"999000999000999000"}

Returns: {message_id, channel_id, author_id, author_name, content, components?, embeds?, attachments?, flags?, timestamp, edited, pinned}. This is a selected message projection, not the entire Discord message. content is unchanged; rich fields are preserved in full when supplied by Discord, including unknown component types. Empty or absent upstream fields stay empty or absent.

Readable text: The human-readable MCP response derives text from original content, nested Text Display components in order, then embed author/title/description/fields/footer. All derived text is fenced as untrusted Discord data; raw structured fields are also untrusted. Attachment and media URLs are metadata only and are not fetched.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channel_id`	Yes	Channel containing the message
`message_id`	Yes	Message 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": {
-      "author_id": {
-        "description": "Discord user ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "author_name": {
-        "type": "string"
-      },
-      "channel_id": {
-        "description": "Discord channel ID (snowflake)",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "content": {
-        "type": "string"
-      },
-      "edited": {
-        "type": "boolean"
-      },
-      "message_id": {
-        "description": "Discord message ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "pinned": {
-        "type": "boolean"
-      },
-      "timestamp": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "message_id",
-      "channel_id",
-      "author_id",
-      "author_name",
-      "content",
-      "timestamp",
-      "edited",
-      "pinned"
-    ],
-    "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": {
+      "attachments": {
+        "description": "Raw attachment metadata; URLs are not fetched",
+        "items": {
+          "additionalProperties": {},
+          "properties": {},
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "author_id": {
+        "description": "Discord user ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "author_name": {
+        "type": "string"
+      },
+      "channel_id": {
+        "description": "Discord channel ID (snowflake)",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "components": {
+        "description": "Complete raw Discord component tree",
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "type": {
+              "maximum": 9007199254740991,
+              "minimum": -9007199254740991,
+              "type": "integer"
+            }
+          },
+          "required": [
+            "type"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "content": {
+        "description": "Original Discord content; may be empty for component-only messages",
+        "type": "string"
+      },
+      "edited": {
+        "type": "boolean"
+      },
+      "embeds": {
+        "description": "Complete raw Discord embeds",
+        "items": {
+          "additionalProperties": {},
+          "properties": {},
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "flags": {
+        "description": "Original Discord message flags, when supplied",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "message_id": {
+        "description": "Discord message ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "pinned": {
+        "type": "boolean"
+      },
+      "timestamp": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "message_id",
+      "channel_id",
+      "author_id",
+      "author_name",
+      "content",
+      "timestamp",
+      "edited",
+      "pinned"
+    ],
+    "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.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable behavior beyond that: it returns a selected projection rather than the full Discord message, preserves rich fields, and flags all derived and raw data as untrusted. It also explains that attachment URLs are metadata only. This is exactly the kind of context that helps an agent interpret results safely.

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

Conciseness4/5

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

The description is longer than average but is well-structured with headers (Purpose, When to use, When NOT to use, Example, Returns, Readable text). Every section adds necessary information, especially the readable text explanation which is non-obvious. It is front-loaded with the purpose, and the length is justified by the complexity of the return projection.

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 two-parameter fetch tool, the description is comprehensive. It explains when to use it, when not to, provides an example, details the return projection and its fields, and warns about untrusted data. The output schema exists, so return structure is also formally defined. Nothing an agent needs to call this correctly and interpret the result 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 has a short description ('Channel containing the message', 'Message to fetch'). The tool description adds an example with sample IDs, but no additional semantic meaning about the parameters themselves. Given full schema coverage, the baseline of 3 is appropriate; the example is a minor enhancement.

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 opens with a precise statement: 'Fetch a single Discord message by ID.' This clearly identifies the verb (fetch), resource (message), and scope (single, by ID). It also differentiates from the sibling messages_read by explicitly stating that reading a window of recent messages is out of scope and routed to that alternative.

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 description includes dedicated 'When to use' and 'When NOT to use' sections. It explicitly tells the agent when to use this tool (inspecting a specific message, verifying existence) and when not to (reading a recent window, then use messages_read). This is direct, actionable guidance with a named alternative.

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

Deploy Server