Skip to main content
Glama
barryyip0625

MCP-Discord

by barryyip0625
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_read_messages

Retrieves messages from a Discord text channel, with optional filters for time range (before, after, around) and a limit on the number of messages (max 100, default 50).

Instructions

Retrieves messages from a Discord text channel. Supports date-based filtering via before/after/around params (accepts snowflake IDs or ISO 8601 dates).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoSnowflake ID or ISO 8601 date (e.g. '2025-03-01T00:00:00Z'). Get messages after this point.
limitNo
aroundNoSnowflake ID or ISO 8601 date (e.g. '2025-03-01T00:00:00Z'). Get messages around this point.
beforeNoSnowflake ID or ISO 8601 date (e.g. '2025-03-01T00:00:00Z'). Get messages before this point.
channelIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.0
    • addedInput schema / properties / after
      Added value: +{
+  "description": "Snowflake ID or ISO 8601 date (e.g. '2025-03-01T00:00:00Z'). Get messages after this point.",
+  "type": "string"
+}
    • addedInput schema / properties / around
      Added value: +{
+  "description": "Snowflake ID or ISO 8601 date (e.g. '2025-03-01T00:00:00Z'). Get messages around this point.",
+  "type": "string"
+}
    • addedInput schema / properties / before
      Added value: +{
+  "description": "Snowflake ID or ISO 8601 date (e.g. '2025-03-01T00:00:00Z'). Get messages before this point.",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full transparency burden. It states that the tool 'retrieves' messages (implying read-only), but it does not mention side effects, required permissions, rate limits, pagination behavior, or whether the operation is idempotent. This is insufficient for a tool that could have security or API-cost implications.

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 two concise sentences. The primary action is front-loaded ('Retrieves messages...'), followed immediately by the key filtering feature. No redundant or filler content is present.

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?

The description covers the core function and filtering capabilities, but it does not describe the output format (no output schema exists) or specify ordering, attachment handling, or pagination beyond the limit parameter. This leaves some context gaps for an agent planning a call, though the essential operation is clear.

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?

Three of five parameters (after, around, before) have detailed descriptions in the schema, and the tool description reinforces their meaning. However, limit and channelId lack descriptions, leaving some ambiguity for agents. The 60% schema coverage is moderate, and the descriptions provided are clear, but the missing ones reduce completeness.

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 clearly states the tool's purpose: 'Retrieves messages from a Discord text channel.' This is a specific verb and resource, and it distinguishes the tool from siblings like discord_search_messages, which presumably performs keyword searches rather than plain retrieval.

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 mentions date-based filtering via before/after/around parameters, but it does not explicitly contrast this with sibling tools such as discord_search_messages or discord_list_pinned_messages. The intended use case is implied (fetching message history) but not explicitly stated.

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