Skip to main content
Glama
piekstra

Slack MCP Server

by piekstra

get_channel_info

Retrieve detailed information about a specific Slack channel using its channel ID to access channel properties and metadata.

Instructions

Get detailed information about a specific Slack channel.

Args: channel_id: The ID of the channel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for get_channel_info: creates SlackClient, calls its get_channel_info method, and returns JSON string of the result.
    @mcp.tool()
    async def get_channel_info(channel_id: str) -> str:
        """
        Get detailed information about a specific Slack channel.
    
        Args:
            channel_id: The ID of the channel
        """
        try:
            client = SlackClient()
            result = await client.get_channel_info(channel_id)
            return json.dumps(result, indent=2)
        except Exception as e:
            return json.dumps({"error": str(e)}, indent=2)
  • SlackClient helper method that makes API request to Slack's conversations.info endpoint to fetch channel details.
    async def get_channel_info(self, channel_id: str) -> Dict[str, Any]:
        """Get detailed information about a specific channel."""
        params = {"channel": channel_id}
        return await self._make_request("GET", "conversations.info", params=params)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves 'detailed information' but doesn't specify what that includes (e.g., channel name, members, purpose), whether it's read-only, requires permissions, or has rate limits. This is a significant gap for a tool with no annotation coverage.

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 appropriately sized and front-loaded, with the core purpose stated first in a clear sentence. The 'Args' section is structured but could be integrated more seamlessly. There's no wasted text, though it could be slightly more polished for optimal efficiency.

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 low complexity (1 parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and incomplete behavioral details, it doesn't fully compensate for the lack of structured data, leaving gaps in usage and transparency.

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 description adds minimal semantics beyond the input schema: it defines 'channel_id' as 'The ID of the channel', which is basic but helpful. With 0% schema description coverage and 1 parameter, this provides some value, but it doesn't explain where to find the ID or its format, keeping it at the baseline for partial compensation.

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 tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific Slack channel'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'list_channels' (which lists channels) or 'get_channel_history' (which retrieves message history), missing an opportunity for full sibling distinction.

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 sibling tools like 'list_channels' for general channel listing or 'get_channel_history' for message history, nor does it specify prerequisites such as needing channel access. This leaves the agent without context for 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/piekstra/slack-mcp-server'

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