Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

read_messages

Read-only

Retrieves readable chat history from a Discord channel, thread, or DM, ordered oldest to newest, with time and ID filters to page through up to 500 messages.

Instructions

Read chat history of a channel, thread or DM in readable form (oldest → newest). Paginates up to 500 messages. Use since/before/after/around to move in time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoInclude full embed text, mentions and ids
afterNoOnly messages after this message ID
limitNoHow many messages (default 50, max 500)
sinceNoOnly messages after this time (ISO8601, e.g. 2026-11-20T00:00:00Z)
untilNoOnly messages before this time (ISO8601)
aroundNoMessages around this message ID
beforeNoOnly messages before this message ID
user_idNoOr: a user ID to DM (opens the DM for you)
channel_idNoChannel/thread/DM ID or a discord.com/channels/… link

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuine context beyond them: results come back in readable/rendered form and are ordered oldest → newest, with a 500-message pagination ceiling. It says nothing about permissions needed to read a channel or how pagination continues past the limit.

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?

Three short sentences with zero filler; the core capability and ordering are front-loaded before pagination and time-navigation hints.

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

Completeness3/5

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

Nine parameters with zero required fields and no output schema make the calling contract non-obvious, yet the description never says what happens if neither channel_id nor user_id is supplied, or how the readable output is shaped. Ordering, pagination and time navigation are covered adequately for a read tool, so it is viable but with clear gaps.

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 every one of the 9 parameters is already documented, including the 'Or: a user ID to DM' alternative for user_id. The description only points at the four time-navigation parameters, adding no syntax or behavior detail beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (read chat history) plus the scope (channel, thread or DM) and the ordering guarantee (oldest → newest). It does not name or contrast with search_messages, so an agent must infer when history-reading differs from searching.

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?

The sentence 'Use since/before/after/around to move in time' is parameter-level guidance rather than when-to-use guidance. There is no statement about when to prefer this over search_messages or list_saved_messages, and no exclusions or prerequisites.

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

Deploy Server

Other Tools