Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by tensakulabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_get_messages

Retrieve messages from a Discord channel using local cache or API. Filter by date range and limit results.

Instructions

Get messages from a channel. Uses local cache if daemon is running, Discord API otherwise.

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_get_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYes
limitNoMax messages (1-100)
sinceNoISO date or datetime e.g. '2026-02-25' or 'yesterday'
untilNoISO date or datetime upper bound

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.9

TDQS

A4/5.0
Behavior4/5

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

Discloses use of local cache vs. Discord API, which is important for performance and freshness. No annotations provided, so description does the job well.

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?

Extremely concise: two sentences that cover purpose and caching behavior, no wasted words.

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?

Provides key context on caching vs API, but lacks details on error handling or return value format (no output schema). Still adequate for a straightforward get operation.

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 75%; the description does not add additional meaning beyond what the schema already provides for parameters like limit, since, and until.

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?

Clearly states 'Get messages from a channel' and is distinct from sibling tools like discord_get_dms or discord_search.

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?

Implies use for retrieving messages with optional time filters, but lacks explicit guidance on when to prefer this over discord_search or other alternatives.

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