Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_channels

Read-only

Lists all channels in a Discord server with full details, including permission overwrites and topics, when given a server ID.

Instructions

List all channels of a server with full details (permission overwrites, topics…). For a compact tree use get_channel_tree. [GET /guilds/{guild_id}/channels]

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_guild_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
permissionsNoPermissions: bitfield string, or names like ["VIEW_CHANNEL","SEND_MESSAGES"]
with_can_link_lobbyNowith can link lobby

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without description help. The description adds payload-level context by noting that results include permission overwrites and topics, but says nothing about volume, pagination, or the meaning of the extra query flags beyond what the schema already states.

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?

Two short sentences plus an endpoint tag, with the core purpose and the differentiator front-loaded. Every clause carries information: what it returns, how it differs from the sibling, and the underlying route.

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 three-parameter read-only list tool with fully described parameters and no output schema, the description tells the agent what kind of payload to expect and when to prefer the alternative. Only minor gaps remain around result size or pagination behavior, which matter little for this tool class.

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%, so guild_id, permissions and with_can_link_lobby are already documented in structured fields; that sets the baseline at 3. The description's mention of 'permission overwrites' hints at the permissions parameter but adds no syntax, default, or interaction detail beyond the schema.

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?

States a specific verb and resource (list all channels of a server) plus a scope qualifier ('with full details (permission overwrites, topics…)'). It explicitly distinguishes itself from get_channel_tree by characterizing that tool as the 'compact tree' option, so an agent can pick the right one without opening a schema.

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

Usage Guidelines4/5

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

Names a concrete alternative and the condition that selects it ('For a compact tree use get_channel_tree'), which is real routing guidance rather than implied usage. It stops short of stating exclusions for the other channel-adjacent siblings (e.g. active threads) or any prerequisites, so it is clear but not fully exhaustive.

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