Skip to main content
Glama
ExoCubeYT

OpenWA MCP Server

by ExoCubeYT

delete_message

Delete a specific message from a WhatsApp chat by providing session and message IDs.

Instructions

Delete a specific message from a WhatsApp chat

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID
messageIdYesID of the message to delete

Implementation Reference

  • Handler function for the 'delete_message' tool. Makes a DELETE request to the OpenWA API at `/sessions/${sessionId}/messages/${messageId}`.
    async ({ sessionId, messageId }) => {
      const data = await openwaClient({
        method: "DELETE",
        path: `/sessions/${sessionId}/messages/${messageId}`,
      });
      return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema for 'delete_message'. Defines required parameters: sessionId (string) and messageId (string).
    {
      description: "Delete a specific message from a WhatsApp chat",
      inputSchema: {
        sessionId: z.string().describe("Session ID"),
        messageId: z.string().describe("ID of the message to delete"),
      },
  • Registration of the 'delete_message' tool on the MCP server via server.registerTool().
    server.registerTool(
      "delete_message",
      {
        description: "Delete a specific message from a WhatsApp chat",
        inputSchema: {
          sessionId: z.string().describe("Session ID"),
          messageId: z.string().describe("ID of the message to delete"),
        },
      },
      async ({ sessionId, messageId }) => {
        const data = await openwaClient({
          method: "DELETE",
          path: `/sessions/${sessionId}/messages/${messageId}`,
        });
        return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The openwaClient helper used by the handler to make HTTP requests to the OpenWA API.
    export async function openwaClient<T = unknown>(opts: RequestOptions): Promise<T> {
      const url = `${BASE_URL}${opts.path}`;
    
      const headers: Record<string, string> = {
        "Content-Type": "application/json",
        "X-API-Key": API_KEY,
      };
    
      const res = await fetch(url, {
        method: opts.method,
        headers,
        body: opts.body ? JSON.stringify(opts.body) : undefined,
      });
    
      const text = await res.text();
    
      if (!res.ok) {
        throw new Error(`OpenWA API ${res.status}: ${text}`);
      }
    
      try {
        return JSON.parse(text) as T;
      } catch {
        return text as T;
      }
    }
  • src/index.ts:15-16 (registration)
    Entry point where registerMessageTools (which registers delete_message) is called.
    registerSessionTools(server);
    registerMessageTools(server);
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the action (delete) but doesn't clarify permanence, reversibility, impact on other participants, or rate limits.

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?

Single sentence with no wasted words. Front-loaded with key action and context.

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 2-parameter tool, the description is adequate but lacks completeness regarding expected behavior or response after deletion. No output schema; could mention if success is indicated.

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 covers 100% of parameters with descriptions. The tool description adds no extra meaning beyond the schema, but the schema itself is sufficient.

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?

Description clearly states the action and object: 'Delete a specific message from a WhatsApp chat'. It distinguishes from sibling tools like 'react_to_message' or 'send_text' by specifying 'delete' and 'message'.

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, no prerequisites or conditions mentioned. Could specify if the message must be yours or if there are permissions needed.

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