Skip to main content
Glama
larrygmaguire-hash

Slack Note Capture MCP Server

slack_post_message

Post messages to Slack channels to enable asynchronous communication, manage threads, and send task notifications between Claude and Slack users.

Instructions

Post a message to a Slack channel. Returns the message timestamp (ts) which can be used to read thread replies later.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idNoThe Slack channel ID. Defaults to configured inbox channel.
textYesThe message text to post.

Implementation Reference

  • The handler implementation for the `slack_post_message` tool.
    case "slack_post_message": {
      const channelId = args.channel_id || DEFAULT_CHANNEL;
      const text = args.text;
    
      if (!channelId) {
        return {
          content: [
            {
              type: "text",
              text: "Error: No channel ID provided and no default channel configured.",
            },
          ],
        };
      }
    
      const result = await slack.chat.postMessage({
        channel: channelId,
        text: text,
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              {
                success: true,
                channel: result.channel,
                ts: result.ts,
                message: result.message?.text,
                hint: "Use the 'ts' value with slack_read_thread or slack_wait_for_reply to monitor for responses.",
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • The tool schema definition for `slack_post_message` inside `ListToolsRequestSchema`.
    {
      name: "slack_post_message",
      description:
        "Post a message to a Slack channel. Returns the message timestamp (ts) which can be used to read thread replies later.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: {
            type: "string",
            description:
              "The Slack channel ID. Defaults to configured inbox channel.",
          },
          text: {
            type: "string",
            description: "The message text to post.",
          },
        },
        required: ["text"],
      },
    },
Behavior4/5

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

No annotations provided, so description carries full burden. It successfully discloses the return value (message timestamp/ts) and its utility for future thread operations, compensating for missing output schema. Does not mention auth requirements or rate limits, but covers the critical output behavior.

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?

Two well-structured sentences. First sentence front-loads the core action; second sentence explains the return value utility. No redundancy or filler—every sentence earns its place.

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

Completeness4/5

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

Given the simple 2-parameter schema and lack of output schema, the description adequately explains the inputs and compensates by describing the return value. Complete enough for invocation, though could briefly mention relationship to slack_post_to_thread for full contextual clarity.

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% (both channel_id and text have descriptions). The description mentions 'Slack channel' and 'message' which maps to parameters, but adds no syntax details, validation rules, or semantic relationships beyond what the schema already provides. Baseline 3 appropriate for high-coverage schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear specific verb 'Post' with resource 'message to a Slack channel'. Implicitly distinguishes from sibling slack_post_to_thread by specifying 'channel' (implying top-level post vs reply), establishing distinct scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies workflow by mentioning the returned ts can be used to read thread replies later, hinting at integration with slack_read_thread. However, lacks explicit guidance on when to use this versus slack_post_to_thread for replies.

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/larrygmaguire-hash/slack-note-capture'

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