Skip to main content
Glama
piekstra

Slack MCP Server

by piekstra

unarchive_channel

Restore archived Slack channels to active status for continued team communication and collaboration.

Instructions

Unarchive a Slack channel.

Args: channel: Channel ID to unarchive

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for unarchive_channel. Decorated with @mcp.tool(), creates SlackClient instance and calls its unarchive_channel method to unarchive the specified channel, returning JSON result.
    @mcp.tool()
    async def unarchive_channel(channel: str) -> str:
        """
        Unarchive a Slack channel.
    
        Args:
            channel: Channel ID to unarchive
        """
        try:
            client = SlackClient()
            result = await client.unarchive_channel(channel)
            return json.dumps(result, indent=2)
        except Exception as e:
            return json.dumps({"error": str(e)}, indent=2)
  • SlackClient helper method that performs the Slack API call to unarchive the channel using conversations.unarchive endpoint.
    async def unarchive_channel(self, channel: str) -> Dict[str, Any]:
        """Unarchive a channel."""
        data = {"channel": channel}
        return await self._make_request("POST", "conversations.unarchive", json_data=data)
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 only states the action without behavioral details. It doesn't disclose permissions needed, side effects (e.g., channel becoming active again), rate limits, or error conditions, which are critical for a mutation tool like this.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main action and uses a clear two-sentence structure. It's efficient with minimal waste, though the parameter explanation could be integrated more smoothly rather than as a separate 'Args:' section.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (simple mutation), lack of annotations, and presence of an output schema, the description is minimally adequate but incomplete. It covers the basic action and parameter but misses behavioral context and usage guidelines, which are important for safe operation.

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 0%, but the description adds the parameter 'channel' with a brief explanation ('Channel ID to unarchive'), providing basic semantics beyond the schema. However, it doesn't specify format (e.g., ID format examples) or constraints, leaving gaps in parameter understanding.

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 ('Unarchive') and resource ('a Slack channel'), making the purpose immediately understandable. It distinguishes from sibling 'archive_channel' by specifying the opposite operation, though it doesn't explicitly mention other related tools like 'create_channel' or 'list_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 on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., channel must be archived first), constraints (e.g., permissions required), or related tools like 'archive_channel' for context, leaving usage unclear beyond the basic action.

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/piekstra/slack-mcp-server'

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