Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_channel_tree

Read-only

Retrieve a Discord server's channel hierarchy as a category-to-channel tree, including types, topics, and unread markers while hiding channels you cannot view.

Instructions

Show a server's channels as a tree (categories → channels) with types, topics and unread markers; hides channels you cannot see.

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": "get_channel_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYes
include_hiddenNoAlso list channels you lack View Channel on
include_threadsNoAdd active threads under their channels

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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. The description adds real value beyond that by disclosing the default permission-based filtering and the fields returned (types, topics, unread markers), but says nothing about ordering, scale or how large guilds 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?

A single dense sentence with the primary behavior front-loaded, followed by output shape and then the filtering default. Every clause contributes; nothing is redundant or padded.

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 read-only listing tool with no output schema, the description correctly supplies the return shape (categories → channels with types, topics, unread markers) and the visibility default. Only the threads behavior and any size/pagination expectations are left unmentioned.

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 67% and two of three params are documented in the schema itself. The description's 'hides channels you cannot see' partially explains include_hidden by contrast, but include_threads is not addressed at all and guild_id is left to inference. Baseline 3 is appropriate given the schema carries most of the burden.

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?

Specific verb ('Show') plus resource ('a server's channels') plus an explicit output shape ('as a tree (categories → channels)'). The hierarchical framing implicitly separates it from single-channel siblings like get_channel, but no sibling is named, so it falls short of a 5.

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: an agent can infer this is the overview tool for a whole guild, and the 'hides channels you cannot see' clause implies the include_hidden escape hatch. There is no explicit when-to-use/when-not or pointer to the single-channel alternatives.

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