Radar noEixo

Delete whatsapp template

delete_whatsapp_template

Destructive

📱 TEMPLATES WABA — Deleta um template WABA pelo nome. A Meta não permite EDITAR o texto de um template já criado (aprovado ou não) — pra corrigir algo (ex: erro de digitação, acento corrompido), a única forma é deletar e criar de novo com create_whatsapp_template.

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": {
      "name": "<name>"
    },
    "name": "delete_whatsapp_template"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Nome exato do template a deletar (obtido via list_whatsapp_templates).
`numero`	No	Etapa 1b — WhatsApp da conta (telefone, ex.: "5548992172321", ou o id em list_agent_profiles → numeros). Os modelos são da conta da Meta de cada número. Vazio = o número principal.
`target_user_id`	No	ID da conta-alvo (opcional; APENAS o admin da plataforma pode usar). Padrão: a conta autenticada.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / numero

Added value: +{
+  "description": "Etapa 1b — WhatsApp da conta (telefone, ex.: \"5548992172321\", ou o id em list_agent_profiles → numeros). Os modelos são da conta da Meta de cada número. Vazio = o número principal.",
+  "type": "string"
+}

First observedOct 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds valuable domain context the annotations cannot convey: the operation is irreversible by design because the underlying platform forbids editing, and recreation is the recovery path. It stops short of saying whether deletion fails if the template is in use or what the tool returns.

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?

Two sentences, front-loaded with the action, then the constraint and the alternative. Zero filler; the emoji/section marker is the only decoration and it aids scanning in a large tool list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and full param coverage in the schema, the description covers the main ambiguity (why delete rather than update). Minor gaps remain: whether deletion is blocked for templates currently in use, and confirmation of the recovered state after success.

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%, so name/numero/target_user_id are already documented in detail, including that name comes from list_whatsapp_templates. The description only restates 'pelo nome' and adds no format, casing, or scoping guidance beyond the schema — baseline 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?

States a specific verb+resource ('Deleta um template WABA pelo nome') with the lookup key, and explicitly names the sibling it relates to (create_whatsapp_template). An agent can distinguish this from delete_email_template, delete_quick_reply, etc. without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both the when and the why-not-otherwise: Meta does not allow editing an already-created template (approved or not), so to fix a typo or corrupted accent the only path is delete + create_whatsapp_template. This is exactly the routing logic an agent needs.

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

All Radar noEixo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?