discord-server-mcp

read_messages

Read-only

Retrieve messages from a Discord channel or thread, newest last, and page through history using before/after message IDs.

Instructions

Read messages of a channel or thread (newest last). Use before/after to page.

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": {
      "channel": "<channel>"
    },
    "name": "read_messages"
  }
}

Input Schema

Name	Required	Description
`bot`	No	Use this bot (name or id) instead of choosing automatically
`after`	No	Message id
`limit`	No
`before`	No	Message id
`server`	No	Server name or id. Optional when the bot is in one server or DISCORD_GUILD_ID is set.
`channel`	Yes	Channel or thread name, id, or message link

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: result ordering ('newest last') and cursor-based paging with before/after. It says nothing about the default page size, truncation, or the shape of returned messages, which keeps it at an adequate-but-not-rich level.

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, zero filler, with the resource scope and ordering stated first and the paging hint second. Every clause carries information an agent can act on.

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?

With six parameters, no output schema, and a read-only profile, the essentials for calling correctly are present via schema plus description. It is thin on what a returned message contains and on interactions between limit and before/after, leaving some gaps for an agent assembling a paging loop.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, so the baseline would be 3. The description earns more by explaining that before/after are pagination cursors rather than mere 'Message id' filters, and by pairing that with the ordering guarantee so the agent understands which direction paging moves.

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 messages of a channel or thread') plus a result ordering ('newest last'), so the agent knows exactly what comes back. It does not differentiate itself from siblings like search_messages or get_message, which an agent might otherwise consider for the same goal.

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 phrase 'Use before/after to page' gives one concrete usage rule for pagination, which is genuinely helpful. However, there is no guidance on when to pick this over search_messages or get_message, nor any prerequisite or exclusion.

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