Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by jslay88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read messages

read_messages

Fetch recent messages from a Discord channel or DM. Use the 'before' parameter to retrieve older messages by specifying a message ID.

Instructions

Read recent messages from a channel or DM. Optionally pass before (a message ID) to page further back in history.

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": "read_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of messages to fetch (1-100)
beforeNoOnly fetch messages before this message ID
channelIdYesThe channel ID to read from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses read-only behavior and pagination via `before`, but omits details like ordering, error handling, or return format. This is adequate for a simple read tool but not rich.

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, front-loaded with the purpose and a single optional usage hint. No redundant or filler content.

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 moderate-complexity read operation with 3 parameters and no output schema, the description covers purpose, scope, and pagination while relying on the schema for parameter details. It does not mention return format but implies it via 'recent messages'. This is sufficiently complete.

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 the schema already documents all parameters. The description adds only minor value by framing `before` as a paging mechanism, which is already implied by the schema's wording. Baseline 3 is appropriate.

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 identifies the action ('Read'), the resource ('messages'), and the scope ('from a channel or DM'), while also noting the pagination option. This fully distinguishes it from siblings like send_message, add_reaction, and list_channels.

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 gives clear context for when to use the tool (reading recent messages, paging back in history) but does not explicitly contrast it with alternatives or mention when not to use it. Sibling names provide some differentiation.

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