Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List channels

list_channels
Read-only

Returns the Discord channels a bot can see, grouped by category with type and topic; filter by text, voice, forum, stage, announcement, or category.

Instructions

The channels in a server the bot can see, grouped by category, with type and topic. Filter by type: text, voice, forum, stage, announcement, category. Channels the bot lacks View Channel on are left out by Discord; hidden_from_bot says how many when any are.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly return channels of this type.
guildNoGuild (server) name or ID. Omit to use the default guild.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=true, and the description adds genuinely useful behavior beyond that: results are category-grouped, permission-invisible channels are silently omitted by Discord, and a hidden_from_bot count signals when omissions occurred. That caveat about incomplete results is exactly the kind of context an agent needs; only pagination or size limits are unaddressed.

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?

Three short sentences, front-loaded with what is returned before the filtering and caveat details. Every sentence carries information: return shape, filter values, and the visibility caveat.

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?

With only two optional parameters, no output schema, and simple annotations, the description covers the essentials well, including the shape of the result and the hidden_from_bot field. It stops short only on result ordering and whether any limits apply to very large servers.

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 100%, so both parameters and the full enum are already documented in the schema. The description restates the type values and the guild default without adding format, syntax, or resolution rules (e.g., name vs. ID precedence) beyond what the schema provides.

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 the resource (channels in a server), the scope ('the bot can see'), the return shape ('grouped by category, with type and topic'), and the filterable types. It is clear what the tool does, though it does not explicitly contrast itself with siblings such as list_threads or list_stages, so an agent must infer that those cover other resource kinds.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: use the type filter to narrow results, omit guild to fall back to the default. There is no explicit statement of when to prefer this over a sibling or when not to call it, leaving routing decisions to inference.

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