discord-mcp

discord_list_messages

Read-onlyIdempotent

List messages from a Discord channel or thread newest first, and paginate or center results with before, after, or around message IDs.

Instructions

List messages from a channel or thread, newest first. Provide before, after, or around snowflake IDs to paginate or center the search window. To fetch a specific message by ID use discord_get_message, and to search messages by text or author across an entire server use discord_search_guild_messages. Page older messages with before=next_before. Bot permissions it may need: View Channel, Read Message History. Read-only; safe to retry.

Input Schema

Name	Required	Description
`after`	No	Get messages posted after this message snowflake ID (use next_after to page forward in time). Use only one of before, after or around
`limit`	No	Max number of messages to return (1-100; default is 50)
`around`	No	Get messages centered around this message snowflake ID. Use only one of before, after or around
`before`	No	Get messages posted before this message snowflake ID (use next_before to page backward in time). Use only one of before, after or around
`channel_id`	Yes	ID of the channel or thread to list messages from

Output Schema

Name	Required	Description	Default
`messages`	Yes
`next_after`	Yes
`next_before`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv0.1.2Nov 4, 2026

addedInput schema / properties / after / description

Added value: +"Get messages posted after this message snowflake ID (use next_after to page forward in time). Use only one of before, after or around"

addedInput schema / properties / around / description

Added value: +"Get messages centered around this message snowflake ID. Use only one of before, after or around"

addedInput schema / properties / before / description

Added value: +"Get messages posted before this message snowflake ID (use next_before to page backward in time). Use only one of before, after or around"

addedInput schema / properties / channel_id / description

Added value: +"ID of the channel or thread to list messages from"

addedInput schema / properties / limit / description

Added value: +"Max number of messages to return (1-100; default is 50)"

addedOutput schema / properties / messages / items / properties / attachments / items / properties / id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
removedOutput schema / properties / messages / items / properties / author / properties / global_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / messages / items / properties / author / properties / global_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
addedOutput schema / properties / messages / items / properties / author / properties / id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
addedOutput schema / properties / messages / items / properties / channel_id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
removedOutput schema / properties / messages / items / properties / edited_timestamp / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / messages / items / properties / edited_timestamp / type
```
Added value: +[
+  "string",
+  "null"
+]
```
addedOutput schema / properties / messages / items / properties / id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
addedOutput schema / properties / messages / items / properties / message_reference / properties / channel_id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
addedOutput schema / properties / messages / items / properties / message_reference / properties / guild_id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```
addedOutput schema / properties / messages / items / properties / message_reference / properties / message_id / description
```
Added value: +"Discord snowflake ID as a numeric string"
```

changedOutput schema / properties / next_after / anyOf

Previous value: -[
-  {
-    "pattern": "^\\d+$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Discord snowflake ID as a numeric string",
+    "pattern": "^\\d+$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / next_before / anyOf

Previous value: -[
-  {
-    "pattern": "^\\d+$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Discord snowflake ID as a numeric string",
+    "pattern": "^\\d+$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv0.1.0Nov 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the safety annotations, it discloses newest-first ordering, cursor-based pagination behavior, and the possible View Channel and Read Message History permission requirements. The final 'Read-only; safe to retry' statement largely repeats the annotations, but the permission and pagination details add substantial operational context.

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 front-loads the action, resource, and ordering, then proceeds logically through pagination, alternatives, permissions, and safety. It is compact and easy to scan, with no digressions; the brief duplicated safety note does not materially reduce its effectiveness.

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?

Together with fully described inputs, safety annotations, and an output schema, it supplies the information needed for correct selection and invocation: scope, ordering, cursor usage, alternatives, and permissions. No material selection or behavioral gap remains for this straightforward read operation.

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 the description mostly restates the documented roles of before, after, and around, including the next_before cursor already mentioned in the schema. It provides a useful workflow summary but little additional parameter meaning, so the high-coverage baseline 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?

The opening sentence gives a specific verb, resource, scope, and ordering: listing channel or thread messages, newest first. It further distinguishes the tool from discord_get_message and discord_search_guild_messages by their respective lookup and search purposes.

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 routes specific-ID lookups to discord_get_message and server-wide text or author searches to discord_search_guild_messages. It also explains when to use before, after, or around and gives a concrete older-page workflow with before=next_before.

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