Skip to main content
Glama
piekstra

Slack MCP Server

by piekstra

set_channel_topic

Update a Slack channel's topic by specifying the channel ID and new topic text to organize discussions and provide context for team members.

Instructions

Set the topic for a Slack channel.

Args: channel: Channel ID topic: New topic text

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYes
topicYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function for set_channel_topic. Registers the tool via @mcp.tool() decorator and implements the logic by calling SlackClient.set_channel_topic.
    @mcp.tool()
    async def set_channel_topic(channel: str, topic: str) -> str:
        """
        Set the topic for a Slack channel.
    
        Args:
            channel: Channel ID
            topic: New topic text
        """
        try:
            client = SlackClient()
            result = await client.set_channel_topic(channel, topic)
            return json.dumps(result, indent=2)
        except Exception as e:
            return json.dumps({"error": str(e)}, indent=2)
  • SlackClient helper method that performs the actual Slack API call to set the channel topic using conversations.setTopic endpoint.
    async def set_channel_topic(self, channel: str, topic: str) -> Dict[str, Any]:
        """Set the topic for a channel."""
        data = {"channel": channel, "topic": topic}
        return await self._make_request("POST", "conversations.setTopic", 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 for behavioral disclosure. While 'Set' implies a mutation operation, it doesn't specify whether this requires admin permissions, what happens if the channel is archived, whether the change is reversible, or any rate limits. The description provides minimal behavioral 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 efficient with zero wasted words. The main purpose is stated in the first sentence, followed by a clean parameter breakdown. Every sentence serves a clear purpose, making it easy to parse quickly.

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 that this is a mutation tool with no annotations but with an output schema, the description provides the minimum viable information about what the tool does. However, for a tool that modifies channel state, it should ideally include more about permissions, constraints, or error conditions to be fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description provides essential parameter information that compensates for the schema gap. It clearly identifies both required parameters ('channel' and 'topic') and provides basic semantic meaning ('Channel ID' and 'New topic text'), though it could elaborate on format constraints or examples.

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 ('Set the topic') and resource ('for a Slack channel'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'set_channel_purpose' or explain how this differs from other channel modification tools.

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 about when to use this tool versus alternatives like 'set_channel_purpose' or other channel management tools. The description lacks any context about prerequisites, permissions needed, or situations where this tool is appropriate versus other channel operations.

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