Skip to main content
Glama

create_channel

Create new Slack channels for team collaboration by specifying a name and privacy setting to organize workspace communication.

Instructions

Create a new channel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesChannel name (lowercase, no spaces)
is_privateNoCreate as private channel

Implementation Reference

  • The main handler function for the 'create_channel' tool. It validates input using createChannelSchema, wraps the Slack conversations.create API call in safeCall, and returns the created channel.
    export async function createChannel(client: SlackClientWrapper, args: unknown) {
      const params = createChannelSchema.parse(args);
    
      return await client.safeCall(async () => {
        const result = await client.getClient().conversations.create({
          name: params.name,
          is_private: params.is_private,
        });
    
        return {
          channel: result.channel,
        };
      });
    }
  • Zod schema used for input validation in the createChannel handler, defining name (required, lowercase alphanum/hyphen/underscore) and optional is_private.
    export const createChannelSchema = z.object({
      name: z.string().min(1).max(80).regex(/^[a-z0-9-_]+$/, 'Channel name must be lowercase with hyphens or underscores'),
      is_private: z.boolean().optional().default(false),
    });
  • src/index.ts:87-105 (registration)
    MCP tool registration: defines name, description, and inputSchema for 'create_channel' in the list_tools response.
    {
      name: 'create_channel',
      description: 'Create a new channel',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Channel name (lowercase, no spaces)',
          },
          is_private: {
            type: 'boolean',
            description: 'Create as private channel',
            default: false,
          },
        },
        required: ['name'],
      },
    },
  • src/index.ts:417-417 (registration)
    Registers the handler mapping for 'create_channel' in the toolHandlers object, wiring it to the CallToolRequest.
    create_channel: (args) => channelTools.createChannel(slackClient, args),
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. 'Create a new channel' implies a write operation but doesn't specify what happens after creation (e.g., whether the creator automatically joins, if there are rate limits, or what permissions are required). This leaves significant gaps for a mutation tool.

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 zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration.

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 no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., channel ID, success status), behavioral constraints, or error conditions, leaving the agent with incomplete operational context.

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 100%, so the schema fully documents both parameters (name format and privacy setting). The description adds no additional parameter information beyond what's in the schema, meeting the baseline score when schema coverage is complete.

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') and resource ('a new channel'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling creation tools (though none exist in the provided list), so it doesn't reach the highest 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. It doesn't mention prerequisites (like needing appropriate permissions), when not to use it, or how it relates to sibling tools like 'list_channels' or 'invite_to_channel'.

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/Hais/slack-bot-mcp'

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