discord-mcp

discord_read_dms

Read-only

Fetch recent direct messages from a Discord user, oldest to newest, to review DM history or verify bot conversations. Returns message IDs, authors, content, embeds, and timestamps.

Instructions

Read the most recent messages from the bot's DM conversation with a user, oldest-to-newest. Returns { messages: [...] } with id, author, content, embed count, timestamp. Read-only.

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": {
      "user_id": "<user_id>"
    },
    "name": "discord_read_dms"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many recent messages to fetch (1–100). Default 20.
`user_id`	Yes	Discord user ID (snowflake) of the DM recipient.

Output Schema

Name	Required	Description	Default
`messages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.3.0Nov 9, 2026

addedOutput schema / properties / messages / items / properties / author_id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / messages / items / properties / webhook_id
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / messages / items / required

Previous value: -[
-  "id",
-  "author",
-  "content",
-  "embeds",
-  "timestamp"
-]New value: +[
+  "id",
+  "author",
+  "author_id",
+  "content",
+  "embeds",
+  "timestamp"
+]

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

Changed6 schema fields changedv2.0.0Jun 27, 2026

addedInput schema / properties / limit / default
```
Added value: +20
```
addedInput schema / properties / limit / maximum
```
Added value: +100
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

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

changedOutput schema / (root)

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

Changed2 schema fields changedv1.6.0May 28, 2026

changedInput schema / properties / limit / description

Previous value: -"1–100, default 20."New value: +"How many recent messages to fetch (1–100). Default 20."

changedInput schema / properties / user_id / description

Previous value: -"The Discord user ID."New value: +"Discord user ID (snowflake) of the DM recipient."

Addedv1.3.0May 1, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and 'Read-only' in the description earns nothing new. The description does add ordering (oldest-to-newest) and the fact that only the most recent messages are returned, but it omits an important operational prerequisite: the bot can only read DMs with a user it already shares a DM channel/guild with. It also doesn't note pagination or that limit is a hard cap of 100 outside the schema.

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?

Two short sentences, front-loaded with the resource and scope, then ordering in the same clause. The return-shape note and 'Read-only' are compact; nothing is padded or redundant enough to distract.

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

Completeness4/5

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

With only two parameters, an output schema present, and annotations covering safety, this description is close to complete for the call itself; the return shape mention is a bonus rather than a requirement. The one gap is the missing note that the bot must already have a DM channel with the target user, which materially affects whether the call can succeed.

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%, including the 1–100 range, default of 20, and the snowflake pattern for user_id, so the baseline is 3. The description adds only the framing that limit selects the 'most recent' messages and that results are ordered oldest-to-newest, which is mild added meaning rather than new parameter detail.

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 (read) plus a precisely scoped resource: the bot's DM conversation with one user. The DM qualifier implicitly separates it from discord_read_messages and discord_search_messages, which operate on channels, so an agent can route correctly without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied by the 'DM conversation with a user' scope; there is no explicit statement of when to prefer this over discord_read_messages, discord_search_messages, or discord_get_message_attachments, and no exclusions. The DM framing carries the selection signal, but the agent must infer it.

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

Deploy Server