Skip to main content
Glama

get-message-read-receipts

Retrieve which users have read a specific message in Zulip to track message visibility and engagement.

Instructions

Get list of users who have read a specific message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
message_idYesUnique message ID to get read receipts for

Implementation Reference

  • The MCP tool handler function: extracts message_id, calls ZulipClient.getMessageReadReceipts(), processes response to include count and user_ids, handles errors.
    async ({ message_id }) => {
      try {
        const result = await zulipClient.getMessageReadReceipts(message_id);
        return createSuccessResponse(JSON.stringify({
          message_id,
          read_by_count: result.user_ids.length,
          user_ids: result.user_ids
        }, null, 2));
      } catch (error) {
        return createErrorResponse(`Error getting read receipts: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • Zod input schema validation for the tool: requires a single 'message_id' parameter (number).
    export const GetMessageReadReceiptsSchema = z.object({
      message_id: z.number().describe("Unique message ID to get read receipts for")
    });
  • src/server.ts:621-637 (registration)
    Registration of the tool with MCP server: specifies name, description, input schema, and handler function.
    server.tool(
      "get-message-read-receipts",
      "Get list of users who have read a specific message.",
      GetMessageReadReceiptsSchema.shape,
      async ({ message_id }) => {
        try {
          const result = await zulipClient.getMessageReadReceipts(message_id);
          return createSuccessResponse(JSON.stringify({
            message_id,
            read_by_count: result.user_ids.length,
            user_ids: result.user_ids
          }, null, 2));
        } catch (error) {
          return createErrorResponse(`Error getting read receipts: ${error instanceof Error ? error.message : 'Unknown error'}`);
        }
      }
    );
  • ZulipClient helper method: makes authenticated GET request to Zulip API endpoint /messages/{messageId}/read_receipts and returns raw response with user_ids array.
    async getMessageReadReceipts(messageId: number): Promise<{ user_ids: number[] }> {
      const response = await this.client.get(`/messages/${messageId}/read_receipts`);
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get list' implies a read-only operation, it doesn't specify whether this requires special permissions, what format the user list returns in, whether it's paginated, or if there are rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple retrieval tool and gets straight to the point without unnecessary elaboration.

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?

For a single-parameter read operation with no output schema, the description provides the basic purpose but lacks important context. Without annotations or output schema, it should ideally specify what the return format looks like (e.g., list of user objects with timestamps) and any prerequisites. The description is minimally adequate but has clear gaps.

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%, with the single parameter 'message_id' well-documented in the schema as 'Unique message ID to get read receipts for'. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 ('Get list') and target resource ('users who have read a specific message'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-message' or 'get-messages', which also retrieve message-related data but for different purposes.

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. With sibling tools like 'get-message' and 'get-messages' available, there's no indication of whether this tool should be used for read receipt tracking specifically or if it's part of a broader message retrieval workflow.

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/avisekrath/zulip-mcp-server'

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