Skip to main content
Glama

discord_find_channel_by_name

Locate Discord channels by name within a guild using partial matching. Input guild ID and channel name to retrieve channel details.

Instructions

Find a channel by name in a guild (partial match supported).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes
nameYes

Implementation Reference

  • The handler logic for 'discord_find_channel_by_name' which fetches channels in a guild and filters them by name.
    case "discord_find_channel_by_name": {
      const guild = await discord.guilds.fetch(validateId(args.guild_id, "guild_id"));
      await guild.channels.fetch();
      const keyword = (args.name as string).toLowerCase();
      const matches = guild.channels.cache
        .filter((c) => c.name.toLowerCase().includes(keyword))
        .map((c) => ({ id: c.id, name: c.name, type: ChannelType[c.type] }));
      return { content: [{ type: "text", text: JSON.stringify(matches, null, 2) }] };
    }
  • The input schema and tool definition for 'discord_find_channel_by_name'.
      name: "discord_find_channel_by_name",
      description: "Find a channel by name in a guild (partial match supported).",
      inputSchema: {
        type: "object",
        properties: {
          guild_id: { type: "string" },
          name: { type: "string" },
        },
        required: ["guild_id", "name"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'partial match supported,' which is useful, but doesn't cover critical aspects like permissions needed, rate limits, error conditions, or what the output looks like (e.g., single channel vs. list). This leaves significant gaps for a tool that likely queries Discord's API.

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, efficient sentence that front-loads the core purpose ('Find a channel by name in a guild') and adds a key detail ('partial match supported') without any wasted words. It's appropriately sized for a simple lookup tool.

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 complexity (a Discord API tool with no annotations or output schema) and low schema coverage, the description is incomplete. It lacks details on permissions, output format, error handling, and differentiation from siblings, making it insufficient for reliable agent use despite its conciseness.

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?

Schema description coverage is 0%, so the description must compensate but adds little. It implies 'name' is for partial matching but doesn't explain 'guild_id' (e.g., what format it expects) or clarify if 'name' is case-sensitive. With 2 undocumented parameters, this falls short of adequately supplementing the schema.

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 ('Find a channel by name') and resource ('in a guild'), with the additional detail 'partial match supported' that adds specificity. However, it doesn't explicitly differentiate from sibling tools like 'discord_list_channels' or 'discord_search_messages', which might also help locate channels.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention sibling tools like 'discord_list_channels' (which lists all channels) or 'discord_search_messages' (which might find channels indirectly), leaving the agent to infer usage context.

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