Skip to main content
Glama
lars-hagen

Slack User MCP Server

by lars-hagen

slack_post_message

Send messages to Slack channels using channel IDs and text content to facilitate team communication and information sharing.

Instructions

Post a new message to a Slack channel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesThe ID of the channel to post to
textYesThe message text to post

Implementation Reference

  • Tool definition including name, description, and input schema for slack_post_message.
    const postMessageTool: Tool = {
      name: "slack_post_message",
      description: "Post a new message to a Slack channel",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: {
            type: "string",
            description: "The ID of the channel to post to",
          },
          text: {
            type: "string",
            description: "The message text to post",
          },
        },
        required: ["channel_id", "text"],
      },
    };
  • MCP CallToolRequest handler case for slack_post_message: validates arguments and invokes SlackClient.postMessage.
    case "slack_post_message": {
      const args = request.params.arguments as unknown as PostMessageArgs;
      if (!args.channel_id || !args.text) {
        throw new Error(
          "Missing required arguments: channel_id and text",
        );
      }
      const response = await slackClient.postMessage(
        args.channel_id,
        args.text,
      );
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Core implementation that sends POST request to Slack chat.postMessage API endpoint.
    async postMessage(channel_id: string, text: string): Promise<any> {
      const response = await fetch("https://slack.com/api/chat.postMessage", {
        method: "POST",
        headers: this.headers,
        body: JSON.stringify({
          channel: channel_id,
          text: text,
          as_user: this.isUserToken
        }),
      });
    
      return response.json();
    }
  • index.ts:535-544 (registration)
    Registration of slack_post_message tool (as postMessageTool) in the ListToolsRequest handler.
    tools: [
      listChannelsTool,
      postMessageTool,
      replyToThreadTool,
      addReactionTool,
      getChannelHistoryTool,
      getThreadRepliesTool,
      getUsersTool,
      getUserProfileTool,
    ],
  • TypeScript interface defining input arguments for slack_post_message tool.
    interface PostMessageArgs {
      channel_id: string;
      text: string;
    }
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. It states the action ('Post a new message') but doesn't cover critical aspects like required permissions, rate limits, error handling, or whether the operation is idempotent. 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, efficient sentence with zero wasted words. It's appropriately sized and front-loaded, directly stating the core functionality 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 incomplete. It doesn't address behavioral traits like side effects, response format, or error conditions, which are crucial for an agent to use this tool effectively in context with its siblings.

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. The description doesn't add any meaning beyond what's in the schema (e.g., it doesn't explain channel ID formats or text limitations), meeting the baseline for high schema coverage.

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 ('Post') and target ('a new message to a Slack channel'), providing a specific verb+resource combination. However, it doesn't differentiate from siblings like 'slack_reply_to_thread' which also posts messages, so it lacks explicit 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 when to choose this over 'slack_reply_to_thread' for threaded replies or other posting-related tools, nor does it specify prerequisites like channel access or permissions.

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/lars-hagen/slack-user-mcp'

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