Skip to main content
Glama
wowjinxy
by wowjinxy

create_text_channel

Create a new text channel in a Discord server to organize conversations, specify topics, and categorize discussions for better community management.

Instructions

Create a new text channel in the specified server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
server_idNo
category_idNo
topicNo
reasonNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function that executes the create_text_channel tool. It fetches the guild, prepares kwargs including name, optional category and topic, calls guild.create_text_channel, and returns a success message.
    @staticmethod
    async def handle_create_text_channel(discord_client, arguments: Dict[str, Any]) -> List[TextContent]:
        """Create a new text channel"""
        guild = await discord_client.fetch_guild(int(arguments["server_id"]))
        
        kwargs = {
            "name": arguments["name"],
            "reason": "Channel created via MCP"
        }
        
        if "category_id" in arguments:
            category = guild.get_channel(int(arguments["category_id"]))
            if category:
                kwargs["category"] = category
        
        if "topic" in arguments:
            kwargs["topic"] = arguments["topic"]
        
        channel = await guild.create_text_channel(**kwargs)
        
        return [TextContent(
            type="text",
            text=f"Created text channel '#{channel.name}' (ID: {channel.id}) in {guild.name}"
        )]
  • The MCP tool registration for 'create_text_channel', defining the tool name, description, and input schema with required server_id and name, optional category_id and topic.
    Tool(
        name="create_text_channel",
        description="Create a new text channel",
        inputSchema={
            "type": "object",
            "properties": {
                "server_id": {
                    "type": "string",
                    "description": "Discord server ID"
                },
                "name": {
                    "type": "string",
                    "description": "Channel name"
                },
                "category_id": {
                    "type": "string",
                    "description": "Optional category ID to place channel in"
                },
                "topic": {
                    "type": "string",
                    "description": "Optional channel topic"
                }
            },
            "required": ["server_id", "name"]
        }
    ),
  • The input schema definition for the create_text_channel tool, specifying properties and requirements.
    inputSchema={
        "type": "object",
        "properties": {
            "server_id": {
                "type": "string",
                "description": "Discord server ID"
            },
            "name": {
                "type": "string",
                "description": "Channel name"
            },
            "category_id": {
                "type": "string",
                "description": "Optional category ID to place channel in"
            },
            "topic": {
                "type": "string",
                "description": "Optional channel topic"
            }
        },
        "required": ["server_id", "name"]
    }
  • Routing logic in call_tool that dispatches 'create_text_channel' to CoreToolHandlers.handle_create_text_channel.
    core_tool_names = [
        "get_server_info", "list_servers", "get_channels", "list_members",
        "get_user_info", "send_message", "read_messages", "add_reaction",
        "add_multiple_reactions", "remove_reaction", "moderate_message",
        "create_text_channel", "delete_channel", "add_role", "remove_role"
    ]
    
    if name in core_tool_names:
        handler_method = f"handle_{name}"
        if hasattr(CoreToolHandlers, handler_method):
            return await getattr(CoreToolHandlers, handler_method)(discord_client, arguments)
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. While 'Create' implies a write/mutation operation, the description doesn't disclose any behavioral traits like required permissions, whether this action is reversible, rate limits, or what happens if the server_id is invalid. It provides minimal context beyond the basic action.

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 extremely concise at just 8 words, front-loaded with the core action, and contains no wasted words. Every word contributes directly to stating the tool's purpose.

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?

For a mutation tool with 5 parameters, 0% schema coverage, no annotations, and multiple sibling channel creation tools, the description is insufficient. While an output schema exists (which reduces the need to describe return values), the description doesn't address critical context like parameter meanings, usage differentiation from siblings, or behavioral implications of creating a channel.

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?

With 0% schema description coverage for 5 parameters, the description provides no information about any parameters. It doesn't explain what 'server_id', 'category_id', 'topic', or 'reason' mean, nor does it clarify that only 'name' is required. The description fails to compensate for the complete lack of schema documentation.

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 ('Create a new text channel') and target resource ('in the specified server'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'create_category', 'create_stage_channel', or 'create_voice_channel' that also create channels but of different types.

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 like 'create_category' or 'create_voice_channel'. There's no mention of prerequisites, permissions needed, or situations where this tool would be preferred over other channel creation tools.

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/wowjinxy/mcp-discord'

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