Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_list_channels

Lists channels in a specified Discord server, with optional filters by channel name or type to find text, voice, forum, or category channels.

Instructions

List channels of a server, filtered by name or type.

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": {
      "guildId": "<guildId>"
    },
    "name": "discord_list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
queryNoCase-insensitive substring of the channel name
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and discloses almost nothing beyond the operation type. It says nothing about permissions required to view channels, whether hidden/inaccessible channels are omitted, result ordering, or how the 200/500 limit interacts with pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the resource precedes the filter details. It is efficient, though the brevity contributes to the gaps noted elsewhere rather than being a virtue in itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four parameters, no annotations, and no output schema, the definition should explain permissions, visibility scoping, and pagination. None of these appear, so an agent can construct a call but cannot predict its completeness or result shape.

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 50%: guildId and query are documented in the schema, while type and limit are not. The description's "filtered by name or type" does link query to name matching and type to the enum, adding a little meaning, but it says nothing about limit behavior or the default of 200.

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 gives a specific verb and resource ("List channels of a server") plus the filtering dimensions (name or type), so the agent knows exactly what comes back. It does not differentiate itself from nearby siblings such as discord_list_threads or discord_channel_info, which keeps it out of 5 territory.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, even though discord_list_threads, discord_list_roles and discord_channel_info sit in the same space. The only hint is the implied context of "of a server", leaving the agent to infer that this is the general enumeration route.

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