WhatsApp Business MCP Server

delete_template

Remove a WhatsApp Business message template by name to manage your template library. This action permanently deletes the template.

Instructions

Delete a message template by name. This action is irreversible.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "template_name": "<template_name>"
    },
    "name": "delete_template"
  }
}

Input Schema

Name	Required	Description	Default
`template_name`	Yes	Name of the template to delete

Implementation Reference

src/whatsapp-client.ts:233-238 (handler)

The actual implementation of the deleteTemplate method that makes the API request.

async deleteTemplate(templateName: string) {
  return this.request(
    `/${this.config.businessAccountId}/message_templates?name=${templateName}`,
    "DELETE"
  );
}

src/index.ts:319-329 (registration)

The MCP tool registration for 'delete_template'.

server.tool(
  "delete_template",
  "Delete a message template by name. This action is irreversible.",
  {
    template_name: z.string().describe("Name of the template to delete"),
  },
  async ({ template_name }) =>
    executeWithHooks("delete_template", { template_name }, config, () =>
      wa.deleteTemplate(template_name)
    )
);

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates the irreversible nature of the action, which is a critical behavioral trait beyond the basic 'delete' operation. However, it lacks details on permissions, error conditions, or confirmation 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?

The description is extremely concise—two sentences with zero waste. It front-loads the core action and follows with a critical warning, making it efficient and well-structured for quick comprehension.

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?

Given the tool's complexity (destructive operation with no annotations or output schema), the description is minimally adequate. It covers the irreversible nature but lacks details on permissions, error handling, or what happens post-deletion, leaving gaps in contextual understanding.

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 schema description coverage is 100%, with the parameter 'template_name' fully documented in the schema. The description adds no additional semantic context beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

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 specific action ('Delete') and resource ('a message template by name'), distinguishing it from sibling tools like 'create_template' and 'list_templates'. It precisely communicates what the tool does without being vague or tautological.

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 does not mention prerequisites, such as needing an existing template, or compare it to related tools like 'update_business_profile' or 'create_template'. Usage context is implied but not explicitly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server