Skip to main content
Glama

delete_whatsapp_workflow

Permanently deletes a WhatsApp workflow after user confirmation. List workflows to identify the correct one, then pass confirm=true to complete deletion.

Instructions

Eliminar workflow — SOLO para BORRAR/ELIMINAR un workflow de WhatsApp de forma permanente. NO usar para editar, modificar, añadir palabras, simular, probar, unir, combinar ni reorganizar workflows. Si el usuario quiere cambiar algo, usar update_whatsapp_workflow. Si dice 'unir' o 'combinar' workflows, NO borrar ninguno — usar update_whatsapp_workflow para fusionar condiciones/acciones en uno existente. Antes de eliminar, SIEMPRE llama a list_whatsapp_workflows para confirmar con el usuario EXACTAMENTE cual workflow quiere borrar por nombre e ID. FLUJO DE CONFIRMACION OBLIGATORIO: Esta accion devolvera success=false con requires_confirmation=true — esto NO es un error, es el paso 1 del flujo normal de confirmacion. Cuando recibas esta respuesta: 1) Describe brevemente al usuario que workflow se eliminara, 2) PARA completamente, 3) NUNCA vuelvas a llamar a esta misma accion — hacerlo INVALIDA el token de confirmacion y rompe el flujo. Los botones de Confirmar/Cancelar aparecen automaticamente en la interfaz del usuario. [mutation] (requiere confirmación: pasar confirm=true para ejecutar)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del workflow a eliminar
confirmNoPasar true para confirmar la ejecución de esta acción peligrosa
Behavior5/5

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

With no annotations, description fully discloses destructive nature, confirmation requirement, two-step flow (first call returns requires_confirmation=true, second call needs confirm=true), and warns against re-calling prematurely. Very transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is long but well-structured: purpose, exclusions, alternative, pre-step, confirmation flow. Every sentence is necessary given the complexity. Slightly verbose but justified.

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

Completeness5/5

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

Covers all agent needs: purpose, exclusions, alternative, mandatory pre-confirmation step, detailed confirmation flow, and behavioral response. No gaps for a destructive tool without output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 2 params (id, confirm) with descriptions. Description adds context about the confirm parameter's role in the confirmation flow and the dangerous nature of the action, enhancing meaning beyond schema.

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 it is for permanently deleting a WhatsApp workflow, with explicit exclusions (editing, modifying, etc.) and naming sibling tool update_whatsapp_workflow. Verb 'Eliminar' and 'SOLO para BORRAR/ELIMINAR' are specific and distinct.

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?

Provides explicit when-to-use (only deletion) and when-not-to-use (editing, etc.), names alternative tool (update_whatsapp_workflow), and outlines a mandatory confirmation flow with pre-step to list workflows. Comprehensive guidance.

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/wazionapps/mcp-server'

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