Skip to main content
Glama
ExoCubeYT

OpenWA MCP Server

by ExoCubeYT

remove_label_from_chat

Remove a label from a specific WhatsApp chat by providing the chat ID, label ID, and session ID.

Instructions

Remove a label from a specific WhatsApp chat

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID
labelIdYesLabel ID
chatIdYesChat ID to remove the label from

Implementation Reference

  • Registration of the 'remove_label_from_chat' tool via server.registerTool, defining its description and inputSchema.
    server.registerTool(
      "remove_label_from_chat",
      {
        description: "Remove a label from a specific WhatsApp chat",
        inputSchema: {
          sessionId: z.string().describe("Session ID"),
          labelId: z.string().describe("Label ID"),
          chatId: z.string().describe("Chat ID to remove the label from"),
        },
      },
      async ({ sessionId, labelId, chatId }) => {
        const data = await openwaClient({
          method: "DELETE",
          path: `/sessions/${sessionId}/labels/${labelId}/chats/${chatId}`,
        });
        return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input schema for remove_label_from_chat: sessionId (string), labelId (string), chatId (string) using Zod validation.
    {
      description: "Remove a label from a specific WhatsApp chat",
      inputSchema: {
        sessionId: z.string().describe("Session ID"),
        labelId: z.string().describe("Label ID"),
        chatId: z.string().describe("Chat ID to remove the label from"),
      },
    },
  • Handler function for remove_label_from_chat that sends a DELETE request to /sessions/{sessionId}/labels/{labelId}/chats/{chatId} via openwaClient.
    async ({ sessionId, labelId, chatId }) => {
      const data = await openwaClient({
        method: "DELETE",
        path: `/sessions/${sessionId}/labels/${labelId}/chats/${chatId}`,
      });
      return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
    }
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 discloses the removal action but does not state whether it is destructive, what side effects occur (e.g., does it affect other chats?), or any authentication or rate limit requirements.

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?

A single, clear sentence with no extraneous words. It efficiently communicates the core action without redundancy.

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 simple tool with 3 parameters and no output schema, the description provides the basic operation. However, it lacks context like required permissions, error handling, or return value. Acceptable for a straightforward action but not fully complete.

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 coverage is 100%: each parameter (sessionId, labelId, chatId) already has a descriptive comment in the schema. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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?

The description clearly states the verb 'Remove', the resource 'label', and the context 'from a specific WhatsApp chat'. It distinguishes well from sibling tools like 'add_label_to_chat' (adds) and 'delete_label' (removes label entirely).

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?

No guidance on when to use this tool versus alternatives like 'add_label_to_chat' or 'delete_label'. No prerequisites or exclusions are mentioned, leaving the agent without context on appropriate 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/ExoCubeYT/openwa-mcp'

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