Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_channel

Read-only

Retrieve a Discord channel, thread, or DM by ID to inspect its raw object for messaging, moderation, or server tasks.

Instructions

Get a channel, thread or DM by ID (raw object). [GET /channels/{channel_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": {
      "channel_id": "<channel_id>"
    },
    "name": "get_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds the underlying endpoint (GET /channels/{channel_id}) and notes the return is a raw object, which is modest but genuine added context; it says nothing about error behavior or what "raw" omits.

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?

One short sentence plus an endpoint tag; the verb and resource are front-loaded and there is no filler. The bracketed endpoint is arguably reference noise for an agent, but it is compact and potentially useful for API mapping.

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?

For a single-parameter read tool with full schema coverage and annotations, most of what an agent needs is present. The notable gap is disambiguation from the many channel-related siblings, especially get_channel_info and get_dm_channel, which the description never addresses.

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% and the single channel_id parameter is already documented as accepting text, voice, thread, forum or DM channels. The description restates the same channel-type list without adding format details, so the baseline 3 applies.

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?

States a specific verb ("Get") and resource ("a channel, thread or DM by ID") with a useful qualifier ("raw object") that hints at the shape of the return. It does not, however, distinguish itself from close siblings such as get_channel_info or get_dm_channel, which an agent must resolve on its own.

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 when-to-use guidance, no statement of when to prefer this over get_channel_info/get_dm_channel, and no prerequisites. The parenthetical "raw object" is the only implicit hint at why one would choose this tool, and it is left unexplained.

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