Discord MCP Extended

discord_read_messages

Fetch messages from a Discord text channel. Set a limit to control how many recent messages to retrieve.

Instructions

Retrieves messages from a Discord text channel with a configurable limit

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": {
      "channelId": "<channelId>"
    },
    "name": "discord_read_messages"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`channelId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.4Aug 9, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the core action and a parameter, but doesn't mention ordering, return format, rate limits, or read-only status. For a read operation, it's likely safe, but the description doesn't explicitly confirm.

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 is a single, concise sentence that gets straight to the point. It's appropriately sized with no filler.

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

Completeness2/5

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

With no output schema or annotations, the description is the only source of context. It explains the core purpose, but lacks detail on return shape, ordering, and any limitations. For a 2-param tool this is insufficient guidance for an agent to confidently invoke the tool and interpret the result.

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

Parameters2/5

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

The input schema already defines limit with constraints and channelId as a string, but neither has descriptions (0% coverage). The description only references a 'configurable limit' without explaining it represents message count or that channelId identifies the target channel. It adds minimal value over the schema.

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 description uses the specific verb 'Retrieves' with a clear resource 'Discord text channel', and the 'configurable limit' adds scope. It distinguishes from siblings like discord_send and discord_delete_message, and while a search tool exists, this explicitly indicates a simple retrieval without filtering.

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

Usage Guidelines4/5

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

The description implies usage for reading messages from a channel, which is clear context. However, it doesn't explicitly mention alternatives or when to prefer this over discord_search_messages, so it falls short of the top tier.

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