MCP Discord Bot Server

discord_read_messages

Fetch recent messages from a Discord channel by channel ID. Returns JSON with author, content, and timestamp for up to 100 messages.

Instructions

Read recent messages from a Discord channel.

Args:
    channel_id: The ID of the channel to read messages from.
    limit: Number of recent messages to return (default: 50, max: 100).

Returns:
    JSON array of message objects with author, content, and timestamp.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Number of recent messages to retrieve. Default is 50, maximum is 100.
`channel_id`	Yes	The ID of the Discord channel to read messages from. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the default (50) and maximum (100) message count and the shape of the response, but says nothing about permissions required, rate limits, or how to page beyond the 100-message cap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the core purpose in a single sentence. The Args/Returns sections are slightly redundant against the schema but are not verbose.

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?

For a two-parameter read tool with an output schema, the description covers purpose, parameters, and return shape adequately. The main gap is pagination guidance for retrieving messages older than the most recent 100.

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 both channel_id and limit are already fully documented in the schema, and the description merely restates them. Baseline 3 applies when the schema does the heavy lifting.

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 recent messages from a Discord channel'), so an agent immediately knows it is a channel-history read. It does not explicitly distinguish itself from the sibling discord_search_messages, which is the only reason it falls short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives such as discord_search_messages, nor any prerequisites (e.g., the bot must be a member of the channel). Usage is only implied by the word 'recent'.

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

Deploy Server