Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_read_messages

Fetch recent messages from a Discord channel or existing DM, newest first, with optional limits and before/after/around filters for targeted message retrieval.

Instructions

Fetch recent messages from a channel or existing DM, newest first.

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

Input Schema

NameRequiredDescriptionDefault
afterNoOnly messages newer than this message id
limitNo
aroundNoMessages around this message id
beforeNoOnly messages older than this message id
channelIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it delivers only the sort order ('newest first'). It says nothing about required permissions (e.g., read-message-history), rate limits, pagination behavior, or whether 'around' is mutually exclusive with 'before'/'after' — all material for a 5-parameter read tool.

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?

A single front-loaded sentence with no filler, and the scoping detail precedes the ordering detail. It is efficient but arguably too terse for the surface area of the tool, with no secondary sentence to carry guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should convey more: what a returned message looks like, how 'around' interacts with the before/after cursors, and what identifiers are acceptable. For a tool with five parameters and no structured supplementary documentation, one sentence leaves real gaps.

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%, with channelId, after, before, and around all documented inline; only 'limit' lacks a schema description but is bounded by default/min/max. The description adds no parameter meaning beyond the schema, which is acceptable given the high coverage baseline.

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 names a specific verb (Fetch) and resource (recent messages) plus scope (a channel or existing DM) and ordering (newest first), so the operation is unambiguous. It does not, however, distinguish itself from siblings such as discord_search_messages or discord_get_message, so an agent must infer the boundary.

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 explicit when-to-use or when-not-to-use statement, and no alternative is named. The word 'recent' hints at a recency-scoped read, but the agent is left to infer why it should pick this over discord_search_messages for retrieval.

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