discord-mcp

discord_get_message

Read-onlyIdempotent

Fetches a single Discord message by channel or thread ID and message ID, returning its author, content, attachments, embeds, reactions, and poll for direct message lookup.

Instructions

Fetch one message by ID from a channel or thread, with its author, content, attachments, embeds, reactions and poll. Use it when you already have the message ID; to read recent history use discord_list_messages, and to find messages by text use discord_search_guild_messages. Bot permissions it may need: View Channel, Read Message History. Read-only; safe to retry.

Input Schema

Name	Required	Description	Default
`channel_id`	Yes	ID of the channel or thread that holds the message
`message_id`	Yes	ID of the message

Output Schema

Name	Required	Description	Default
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.1.2Nov 4, 2026
- addedInput schema / properties / channel_id / description
```
Added value: +"ID of the channel or thread that holds the message"
```
- addedInput schema / properties / message_id / description
```
Added value: +"ID of the message"
```
- addedOutput schema / properties / message / properties / attachments / items / properties / id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
- removedOutput schema / properties / message / properties / author / properties / global_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / message / properties / author / properties / global_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / message / properties / author / properties / id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
- addedOutput schema / properties / message / properties / channel_id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
- removedOutput schema / properties / message / properties / edited_timestamp / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / message / properties / edited_timestamp / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / message / properties / id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
- addedOutput schema / properties / message / properties / message_reference / properties / channel_id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
- addedOutput schema / properties / message / properties / message_reference / properties / guild_id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
- addedOutput schema / properties / message / properties / message_reference / properties / message_id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
First observedv0.1.0Nov 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is largely covered. The description still adds real value by naming the bot permissions required (View Channel, Read Message History) and confirming retry safety, though it does not discuss error cases such as a deleted or inaccessible message.

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?

Three tight sentences, front-loaded with what the tool returns and followed by routing guidance. The closing "Read-only; safe to retry" largely duplicates the annotation hints, a small redundancy but no loss of clarity.

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 read tool with an output schema, this covers everything needed: what it returns, when to pick it, which siblings to use otherwise, and permission prerequisites. No significant gaps remain for an agent to call 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 coverage is 100%, with both parameters documented, including that channel_id may be a channel or thread. The description's phrasing restates that rather than adding format, ordering, or validation detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Fetch one message by ID") and even enumerates what comes back: author, content, attachments, embeds, reactions, poll. An agent can distinguish it immediately from discord_list_messages and discord_search_guild_messages, which are named explicitly.

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?

Gives an explicit when-to-use condition ("when you already have the message ID") plus two named alternatives for the adjacent cases: recent history and text search. Nothing is left to inference about routing between the three read tools.

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