Skip to main content
Glama

discord_get_forum_channels

Retrieve all forum channels from a Discord guild to manage discussions and organize topics within the server.

Instructions

List all forum channels in a guild.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes

Implementation Reference

  • Handler implementation for the discord_get_forum_channels tool.
    case "discord_get_forum_channels": {
      const guild = await discord.guilds.fetch(validateId(args.guild_id, "guild_id"));
      const channels = await guild.channels.fetch();
      const forums = [...channels.values()]
        .filter((c) => c && c.type === ChannelType.GuildForum)
        .map((c) => ({
          id: c!.id,
          name: c!.name,
          topic: (c as ForumChannel).topic,
          parentId: c!.parentId,
        }));
      return { content: [{ type: "text", text: JSON.stringify(forums, null, 2) }] };
    }
  • Tool definition and input schema for discord_get_forum_channels.
    {
      name: "discord_get_forum_channels",
      description: "List all forum channels in a guild.",
      inputSchema: {
        type: "object",
        properties: {
          guild_id: { type: "string" },
        },
        required: ["guild_id"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('List all'), implying it is likely non-destructive, but does not specify permissions required, rate limits, pagination, or output format. This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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?

The description is a single, clear sentence with no wasted words. It is front-loaded with the core action and resource, making it efficient and easy to parse, though this conciseness comes at the cost of completeness in other dimensions.

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?

Given the lack of annotations, 0% schema coverage, and no output schema, the description is insufficient for a tool with one parameter. It does not address behavioral aspects like permissions or output format, nor does it provide parameter details, leaving the agent with inadequate context for effective use.

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

Parameters2/5

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

The input schema has 0% description coverage, with one required parameter 'guild_id' undocumented. The description mentions 'in a guild', which hints at the parameter's role but does not explain what a 'guild_id' is, its format, or how to obtain it. This adds minimal semantic value beyond the schema's structure.

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 clearly states the action ('List all') and resource ('forum channels in a guild'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'discord_list_channels' or 'discord_list_forum_threads', which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'discord_list_channels' (which might include all channel types) or 'discord_list_forum_threads' (which lists threads within forums). There is no mention of prerequisites, exclusions, or contextual usage, leaving the agent to infer based on tool names alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server