Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by jslay88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List channels

list_channels

Get a full list of channels in a Discord server, including unique IDs and channel types. Identify specific channels for messaging, administration, or bot automation.

Instructions

List channels in a Discord server, including their IDs and types.

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": {
      "serverId": "<serverId>"
    },
    "name": "list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYesThe Discord server (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. However, it only mentions the output (IDs and types) and does not state whether this is read-only, whether permissions are needed, or how errors or empty results are handled.

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 a single, concise sentence that is front-loaded with the verb and resource. Every word earns its place, and there is no redundancy or unnecessary detail.

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?

For a simple list operation with one parameter and no output schema, the description is mostly complete. It states the output content (IDs and types), which is useful given no output schema. However, it omits any mention of limitations, such as whether all channel types are included or if the bot must be a server member.

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 schema already provides complete coverage (100%) for the single parameter serverId, including its description. The tool description adds no further semantic meaning beyond what the schema already states, so it meets the baseline without exceeding it.

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?

The description clearly states the action ('List channels') and the resource ('in a Discord server'), and adds that it returns IDs and types. This distinguishes it from sibling tools like list_servers and get_server_info, which operate on servers, not channels.

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. It does not mention any filters, prerequisites, or cases where another tool would be more appropriate. The description only states what it does, not when to use it.

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