Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by jaimenbell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_channels

Retrieve every channel in a Discord server, including categories and voice channels, using the guild ID. Quickly map your server's structure for navigation or audits.

Instructions

List all channels (every type, including categories and voice channels) in a Discord guild.

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

Input Schema

NameRequiredDescriptionDefault
guild_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It implies a read-only operation by stating 'list', but does not explicitly disclose non-destructive behavior, authentication needs, or rate limits. For a simple list tool, this is adequate but not enhanced.

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?

One sentence that is clear, front-loaded with the main purpose, and contains no unnecessary words. Highly efficient.

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?

Given the tool's simplicity (1 parameter, output schema exists), the description is nearly complete. It could mention behavior when no channels exist or pagination, but these are minor omissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'guild_id' is not described in the schema (0% coverage), but the description explains it by stating the tool lists channels 'in a Discord guild', effectively clarifying the parameter's role. The description compensates well for the lack of schema documentation.

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?

Description clearly states the action (list), resource (all channels including categories and voice channels), and context (Discord guild). It's specific and distinguishes the tool from potential alternatives.

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?

Description implies usage context (Discord guild) but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. Since no sibling tools are listed, the lack of exclusions is acceptable but still minimal.

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