Skip to main content
Glama
Sign In
@striderlabs/mcp-discord

@striderlabs/mcp-discord

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_messages

Retrieve recent messages from any Discord channel by ID. Set a limit and use before_message_id for pagination.

Instructions

Get recent messages from a Discord channel

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of messages to fetch (1-100, default: 50)
channel_idYesThe Discord channel ID
before_message_idNoFetch messages before this message ID (for pagination)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but it only says 'get recent messages.' It does not disclose ordering, pagination behavior, channel access requirements, rate limits, or what the response contains.

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 one short, front-loaded sentence with no filler or redundancy. It efficiently states the core purpose without repeating the tool name verbatim.

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?

Without annotations or an output schema, the description leaves out important context about return values, message ordering, pagination implications, and how this tool relates to search_messages or get_dms. An agent has enough to attempt the call but not enough to use it confidently in varied scenarios.

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?

The input schema covers all three parameters with descriptions and defaults, so the schema carries the parameter-semantics load. The description adds no additional meaning beyond what the schema already provides, which matches the baseline for high schema coverage.

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 resource (Discord channel) and action (get recent messages), which clearly distinguishes it from send_message and get_servers. It does not explicitly contrast with search_messages, but 'recent messages' gives a usable scope.

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?

No guidance is provided about when to use get_messages versus search_messages or get_dms. The word 'recent' implies a usage context, but there are no exclusions, alternatives, or conditions such as pagination scenarios.

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