Skip to main content
Glama
discord-mcp-lite

discord-mcp-lite

list_channels

Read-only

Lists readable text, announcement, forum, and media channels in a Discord guild so you can find where to read or monitor messages. Threads are excluded; use list_threads for those.

Instructions

List readable text, announcement, forum, and media channels in a guild. Threads are not included; use list_threads.

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_idYesGuild id from list_guilds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description still adds value beyond that by disclosing which channel types are returned and that only 'readable' channels qualify, implying permission-based filtering of results. Pagination or result-size behavior is not mentioned, which keeps it from a 5.

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, zero filler. The positive scope comes first and the exclusion/alternative follows, so the most useful information is front-loaded.

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 single-parameter read-only list tool with annotations and no output schema, the definition covers scope, filtering semantics, and the thread exclusion. Only result-set behavior (ordering, pagination) is left unspecified, which is a small residual gap.

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?

With one parameter and 100% schema description coverage ('Guild id from list_guilds'), the schema already carries the semantics. The description references the guild scope but adds no format or sourcing detail beyond what the schema states, so the baseline of 3 applies.

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 ('List') and resource ('readable text, announcement, forum, and media channels in a guild'), and the channel-type enumeration makes the scope unambiguous. It also explicitly draws the boundary against the sibling list_threads, so an agent can distinguish the two without opening schemas.

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?

Gives an explicit exclusion plus the correct alternative: 'Threads are not included; use list_threads.' This is real routing guidance rather than implicit context. It does not address when to prefer find_channel for a single known channel, but that gap is minor for a simple list tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.