Skip to main content
Glama

waha_star_message

Mark messages as starred or remove star status in WhatsApp chats to organize important conversations and highlight key information.

Instructions

Star or unstar a message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chatIdYesChat ID (format: number@c.us)
messageIdYesMessage ID to star/unstar
starYesTrue to star the message, false to unstar

Implementation Reference

  • Executes the waha_star_message tool by validating input parameters, calling the WAHAClient.starMessage method, and returning a formatted success response.
    private async handleStarMessage(args: any) {
      const chatId = args.chatId;
      const messageId = args.messageId;
      const star = args.star;
    
      if (!chatId) {
        throw new Error("chatId is required");
      }
    
      if (!messageId) {
        throw new Error("messageId is required");
      }
    
      if (star === undefined) {
        throw new Error("star is required");
      }
    
      await this.wahaClient.starMessage({
        chatId,
        messageId,
        star,
      });
    
      return {
        content: [
          {
            type: "text",
            text: star
              ? `Successfully starred message ${messageId} in chat ${chatId}.`
              : `Successfully unstarred message ${messageId} in chat ${chatId}.`,
          },
        ],
      };
    }
  • Underlying WAHA API client method that performs the HTTP PUT request to star or unstar the specified message in the WAHA WhatsApp HTTP API.
    async starMessage(params: {
      chatId: string;
      messageId: string;
      star: boolean;
    }): Promise<void> {
      const { chatId, messageId, star } = params;
    
      if (!chatId) {
        throw new WAHAError("chatId is required");
      }
    
      if (!messageId) {
        throw new WAHAError("messageId is required");
      }
    
      const endpoint = `/api/${this.session}/chats/${encodeURIComponent(
        chatId
      )}/messages/${encodeURIComponent(messageId)}/star`;
    
      const body = {
        star,
      };
    
      await this.request<void>(endpoint, {
        method: "PUT",
        body: JSON.stringify(body),
      });
    }
  • JSON schema defining the input parameters, types, descriptions, and required fields for the waha_star_message tool.
      name: "waha_star_message",
      description: "Star or unstar a message.",
      inputSchema: {
        type: "object",
        properties: {
          chatId: {
            type: "string",
            description: "Chat ID (format: number@c.us)",
          },
          messageId: {
            type: "string",
            description: "Message ID to star/unstar",
          },
          star: {
            type: "boolean",
            description: "True to star the message, false to unstar",
          },
        },
        required: ["chatId", "messageId", "star"],
      },
    },
  • src/index.ts:1089-1090 (registration)
    Registration of the tool handler in the MCP CallToolRequestSchema switch statement, dispatching calls to handleStarMessage.
    case "waha_star_message":
      return await this.handleStarMessage(args);
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 but doesn't mention permissions required, side effects (e.g., whether starring is visible to others), error conditions, or what happens on success/failure. For a mutation tool, this lack of detail is a significant gap.

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 front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place.

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 cover behavioral aspects like permissions, side effects, or response format. Given the complexity of modifying message states, more context is needed to help the agent use this tool effectively.

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 input schema has 100% description coverage, clearly documenting all three parameters (chatId, messageId, star). The description doesn't add any semantic context beyond what's in the schema (e.g., format details or usage examples), so it meets 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 ('star or unstar') and resource ('a message'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'waha_pin_message' or 'waha_react_to_message', which are related message interaction tools, so it doesn't reach the highest 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. It doesn't mention prerequisites (e.g., needing chat and message IDs), compare to similar tools like 'waha_pin_message', or specify use cases for starring vs. unstarring. This leaves the agent with minimal context for decision-making.

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