Skip to main content
Glama

zulip_post_message

Send messages to Zulip channels with specified topics to communicate within team workspaces.

Instructions

Post a new message to a Zulip channel (stream)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_nameYesThe name of the stream to post to
topicYesThe topic within the stream
contentYesThe message content to post

Implementation Reference

  • Executes the zulip_post_message tool by validating input arguments (channel_name, topic, content), calling the ZulipClient's sendStreamMessage method, and returning the JSON-stringified response.
    case "zulip_post_message": {
      const args = request.params.arguments as unknown as PostMessageArgs;
      if (!args.channel_name || !args.topic || !args.content) {
        throw new Error(
          "Missing required arguments: channel_name, topic, and content"
        );
      }
      const response = await zulipClient.sendStreamMessage(
        args.channel_name,
        args.topic,
        args.content
      );
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Defines the Tool metadata for zulip_post_message, including name, description, and input schema with required properties channel_name, topic, and content.
    const postMessageTool: Tool = {
      name: "zulip_post_message",
      description: "Post a new message to a Zulip channel (stream)",
      inputSchema: {
        type: "object",
        properties: {
          channel_name: {
            type: "string",
            description: "The name of the stream to post to",
          },
          topic: {
            type: "string",
            description: "The topic within the stream",
          },
          content: {
            type: "string",
            description: "The message content to post",
          },
        },
        required: ["channel_name", "topic", "content"],
      },
    };
  • index.ts:539-547 (registration)
    Registers the zulip_post_message tool (as postMessageTool) in the list of tools returned by the ListToolsRequest handler.
      listChannelsTool,
      postMessageTool,
      sendDirectMessageTool,
      addReactionTool,
      getChannelHistoryTool,
      getTopicsTool,
      subscribeToChannelTool,
      getUsersTool,
    ],
  • ZulipClient helper method that constructs the message parameters and calls the Zulip JS client's messages.send to post the message to the specified stream and topic.
    async sendStreamMessage(streamName: string, topic: string, content: string) {
      try {
        const params = {
          to: streamName,
          type: "stream",
          topic: topic,
          content: content,
        };
        
        return await this.client.messages.send(params);
      } catch (error) {
        console.error("Error sending stream message:", error);
        throw error;
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a 'Post' operation (implying a write/mutation) but doesn't cover important aspects like authentication requirements, rate limits, error conditions, or what happens on success (e.g., message ID returned). This is inadequate for a mutation tool with zero 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.

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded with the essential information.

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 insufficient. It doesn't explain what the tool returns, error handling, or behavioral constraints. Given the complexity of posting messages in a chat system, more context about permissions, formatting, or response format would be needed for completeness.

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 schema description coverage is 100%, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema, which meets the baseline expectation when schema coverage is high.

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 a new message') and target resource ('to a Zulip channel (stream)'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'zulip_send_direct_message', which would require a 5 score.

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 like 'zulip_send_direct_message' or 'zulip_add_reaction'. It also doesn't mention prerequisites such as needing to be subscribed to the channel or having appropriate permissions, leaving usage context unclear.

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/Monadical-SAS/zulip-mcp'

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