Skip to main content
Glama
ExoCubeYT

OpenWA MCP Server

by ExoCubeYT

delete_label

Deletes a specified label from a WhatsApp session using session ID and label ID.

Instructions

Delete a label from the WhatsApp session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID
labelIdYesLabel ID to delete

Implementation Reference

  • Handler function that executes the delete_label logic: sends a DELETE request to /sessions/{sessionId}/labels/{labelId} via openwaClient.
      async ({ sessionId, labelId }) => {
        const data = await openwaClient({
          method: "DELETE",
          path: `/sessions/${sessionId}/labels/${labelId}`,
        });
        return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Schema definition for delete_label: requires sessionId (string) and labelId (string).
    {
      description: "Delete a label from the WhatsApp session",
      inputSchema: {
        sessionId: z.string().describe("Session ID"),
        labelId: z.string().describe("Label ID to delete"),
      },
    },
  • Registration of the delete_label tool using server.registerTool, within the registerLabelTools function.
    server.registerTool(
      "delete_label",
      {
        description: "Delete a label from the WhatsApp session",
        inputSchema: {
          sessionId: z.string().describe("Session ID"),
          labelId: z.string().describe("Label ID to delete"),
        },
      },
      async ({ sessionId, labelId }) => {
        const data = await openwaClient({
          method: "DELETE",
          path: `/sessions/${sessionId}/labels/${labelId}`,
        });
        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, and the description lacks information about behavioral traits such as irreversibility, required permissions, or side effects of deleting a label.

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 concise sentence that is front-loaded and contains no superfluous words.

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 the lack of annotations and output schema, the description is too minimal for a deletion tool. It should include details about irreversibility, permissions, or effects on related data.

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%, with both parameters described in the input 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 'delete' and the resource 'label' from 'WhatsApp session', distinguishing it from sibling tools like create_label, get_labels, and add_label_to_chat.

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 is provided on when to use this tool versus alternatives, nor any prerequisites or context for deletion (e.g., label must exist, session must be active).

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