mcp-discord

discord_list_messages

Retrieve recent messages from Discord channels with pagination options to navigate conversation history efficiently.

Instructions

Fetch recent messages from a channel. Paginate with before/after/around cursors. Default limit is 50, max 100.

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_id": "<channel_id>"
    },
    "name": "discord_list_messages"
  }
}

Input Schema

Name	Required	Description
`channel_id`	Yes
`limit`	No	Number of messages to fetch (1-100, default 50).
`before`	No	Return messages before this message ID.
`after`	No	Return messages after this message ID.
`around`	No	Return messages around this message ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

A3.5/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 burden of behavioral disclosure. It effectively describes key behavioral traits: pagination mechanism (using cursors), default limit (50), and maximum limit (100). However, it doesn't cover other important aspects like rate limits, authentication requirements, error conditions, or what the return format looks like (e.g., message objects with content, timestamps, authors). The description adds value but leaves significant gaps for a tool with no annotation support.

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 perfectly concise and front-loaded: the first sentence states the core purpose, followed by essential behavioral details in subsequent clauses. Every sentence earns its place by providing critical information about pagination and limits without any redundant or vague language. The structure efficiently communicates what's needed in minimal space.

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?

Given the complexity (5 parameters, no annotations, no output schema), the description is moderately complete. It covers the basic operation, pagination mechanism, and limits adequately. However, for a tool with no output schema, it should ideally describe what the return values look like (e.g., array of message objects with fields). The absence of annotations means the description should also address safety/authentication concerns, which it doesn't. It's sufficient for basic use but incomplete for full agent understanding.

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 80% (4 out of 5 parameters have descriptions), so the baseline is 3. The description adds some context by mentioning that before/after/around are 'cursors' for pagination and specifying the default/max for limit, which complements the schema's numeric range description. However, it doesn't provide additional meaning for channel_id or clarify the mutual exclusivity/relationships between the pagination parameters beyond what the schema already indicates.

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?

The description clearly states the action ('Fetch recent messages') and resource ('from a channel'), making the purpose immediately understandable. It distinguishes itself from siblings like discord_get_message (singular) and discord_send_message, though it doesn't explicitly contrast with discord_bulk_delete_messages which also operates on multiple messages. The description is specific but could be slightly more differentiated from similar list operations.

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 description implies usage through mention of pagination parameters (before/after/around) and default/max limits, suggesting when to use this for retrieving message batches. However, it doesn't explicitly state when to choose this over alternatives like discord_get_message for single messages or discord_list_active_threads for thread content. No clear exclusions or prerequisites are provided.

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