Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_get_message

Fetch a single Discord message using its channel and message IDs to inspect content, author, timestamps, or reply context.

Instructions

Fetch one message by id.

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>",
      "messageId": "<messageId>"
    },
    "name": "discord_get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYesDiscord id (snowflake)
messageIdYes

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?

With no annotations, the description carries the full burden, and it only implies a safe read via the word "Fetch". It says nothing about required permissions to view the channel, error behavior for deleted or inaccessible messages, embed/attachment handling, or response shape — all material for a Discord message lookup.

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 zero filler. It is efficient, though the terseness borders on under-specification rather than tight writing.

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 tool is simple (two required id parameters, no output schema, no nested objects), so a one-line description is close to sufficient. Still, for a Discord read it should mention channel-access requirements and the fact that deleted messages will fail, which would fully complete the picture.

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 coverage is 50%, but the second parameter is a $ref to channelId, which is documented as a Discord snowflake, so both required ids are effectively described in the schema. The description adds nothing beyond "by id" — no note that channelId must be the parent channel of the message, which would be genuinely useful context.

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 gives a specific verb and resource ("Fetch one message") plus a scope qualifier ("by id"), so an agent knows exactly what it retrieves. It does not explicitly differentiate itself from siblings such as discord_get_user or discord_get_member, but the resource noun is unambiguous.

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 guidance on when to use this tool versus alternatives, no preconditions (e.g. channel access), and no note about what happens when the message id is invalid or the message was deleted. The only implied usage is the obvious 'you have a message id and want its content'.

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