Skip to main content
Glama

waha_mark_chat_unread

Mark a WhatsApp chat as unread to add an unread indicator for later review. Specify the chat ID to apply this status.

Instructions

Mark a chat as unread. This adds an unread indicator to the chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chatIdYesChat ID (format: number@c.us)

Implementation Reference

  • src/index.ts:313-326 (registration)
    Registration of the 'waha_mark_chat_unread' tool in the ListToolsRequestSchema handler, including input schema definition.
    {
      name: "waha_mark_chat_unread",
      description: "Mark a chat as unread. This adds an unread indicator to the chat.",
      inputSchema: {
        type: "object",
        properties: {
          chatId: {
            type: "string",
            description: "Chat ID (format: number@c.us)",
          },
        },
        required: ["chatId"],
      },
    },
  • Primary MCP tool handler: extracts chatId from arguments, calls WAHAClient.markChatUnread(), returns formatted success response.
      const chatId = args.chatId;
    
      if (!chatId) {
        throw new Error("chatId is required");
      }
    
      await this.wahaClient.markChatUnread(chatId);
    
      return {
        content: [
          {
            type: "text",
            text: `Successfully marked chat ${chatId} as unread.`,
          },
        ],
      };
    }
  • WAHAClient helper method: performs HTTP POST to WAHA API endpoint /api/{session}/chats/{chatId}/unread to mark the chat as unread.
     * Mark a chat as unread
     * POST /api/:session/chats/:chatId/unread
     */
    async markChatUnread(chatId: string): Promise<void> {
      if (!chatId) {
        throw new WAHAError("chatId is required");
      }
    
      const endpoint = `/api/${this.session}/chats/${encodeURIComponent(
        chatId
      )}/unread`;
    
      await this.request<void>(endpoint, {
        method: "POST",
      });
    }
  • src/index.ts:1076-1076 (registration)
    Tool dispatch/registration in the CallToolRequestSchema switch statement.
    return await this.handleMarkChatUnread(args);
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. It states the action but doesn't disclose behavioral traits like whether this is a mutation (implied by 'Mark'), if it requires specific permissions, what happens on failure, or if there are side effects like notifications. The description is minimal and lacks operational context.

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 two sentences, front-loaded with the core action, and has zero wasted words. It efficiently conveys the purpose without redundancy or unnecessary detail, making it highly concise and well-structured.

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?

Given no annotations and no output schema, the description is incomplete for a mutation tool. It doesn't explain what the tool returns (e.g., success/failure status), error conditions, or behavioral nuances. For a tool that likely alters chat state, more context is needed to ensure safe and correct usage.

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 'chatId' fully documented in the schema. The description adds no additional meaning about the parameter beyond what's in the schema, so it meets the baseline of 3 for high schema coverage without extra value.

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 ('Mark a chat as unread') and the effect ('adds an unread indicator to the chat'), which is specific and unambiguous. However, it doesn't explicitly differentiate from its sibling 'waha_mark_chat_read', though the naming makes the distinction obvious.

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 'waha_mark_chat_read' or other chat management tools. It lacks context about prerequisites, such as whether the chat must exist or be accessible, or any constraints on usage.

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/seejux/waha-whatsapp-mcp'

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