Skip to main content
Glama

archive_channel

Archive Slack channels to organize your workspace by removing inactive channels from the active list.

Instructions

Archive a channel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesChannel ID to archive

Implementation Reference

  • The main handler function that executes the archiving of a Slack channel using the conversations.archive API after parsing and validating the input arguments with archiveChannelSchema.
    export async function archiveChannel(client: SlackClientWrapper, args: unknown) {
      const params = archiveChannelSchema.parse(args);
    
      return await client.safeCall(async () => {
        await client.getClient().conversations.archive({
          channel: params.channel,
        });
    
        return {
          ok: true,
          channel: params.channel,
        };
      });
    }
  • Zod schema defining the input validation for the archive_channel tool, requiring a valid channel ID.
    export const archiveChannelSchema = z.object({
      channel: channelIdSchema,
    });
  • src/index.ts:418-418 (registration)
    Registers the handler for the 'archive_channel' tool in the toolHandlers map, delegating to the archiveChannel function from channelTools with the Slack client.
    archive_channel: (args) => channelTools.archiveChannel(slackClient, args),
  • src/index.ts:106-119 (registration)
    Registers the 'archive_channel' tool in the tools list for the list_tools MCP request, providing name, description, and input schema for discovery.
    {
      name: 'archive_channel',
      description: 'Archive a channel',
      inputSchema: {
        type: 'object',
        properties: {
          channel: {
            type: 'string',
            description: 'Channel ID to archive',
          },
        },
        required: ['channel'],
      },
    },
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 'archive' implies a mutation (likely destructive or state-changing), the description doesn't clarify whether this action is reversible, what permissions are required, how it affects channel accessibility, or what happens to existing messages. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 three words, with zero wasted language. It's front-loaded with the core action and resource, making it efficient for quick comprehension. Every word earns its place without redundancy.

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 that this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain the behavioral implications (e.g., reversibility, permissions), return values, or error conditions. For a tool that likely changes system state, this leaves critical gaps for an AI agent to use it effectively.

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?

The input schema has 100% description coverage, with the single parameter 'channel' documented as 'Channel ID to archive'. The description doesn't add any meaning beyond this, such as format examples or constraints on valid channel IDs. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 ('archive') and the resource ('a channel'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential siblings like 'delete_message' or 'update_message' that might also modify channel state, leaving some ambiguity about its specific role in the toolset.

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 (e.g., needing admin permissions), when archiving is appropriate versus deleting, or how it differs from tools like 'delete_message' or 'update_message' that might affect channel content. This leaves the agent with insufficient context for optimal tool selection.

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