Arara MCP

Official

Overview Schema Source Related Servers Discussions Admin

delete_automation

DestructiveIdempotent

Permanently delete a WhatsApp automation with a dry-run preview by default; deletion requires a second call with dryRun=false after approval. To stop it, use set_automation_active active=false.

Instructions

Permanently delete an automation. Dry run by default: it shows what would be removed (name, active state, stats) and deletes only when called again with dryRun=false after the user approves. To just stop it, prefer set_automation_active with active=false.

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

Input Schema

Name	Required	Description	Default
`dryRun`	No
`automationId`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv6.0.1Nov 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Although annotations already mark the tool as destructive and non-read-only, the description adds substantial behavioral context: deletion is permanent, dry run is default, dry run returns name, active state, and stats, and deletion requires explicit confirmation via dryRun=false.

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 three tightly written sentences. It front-loads the destructive action, then explains the safe dry-run workflow, then points to the less destructive alternative without redundant wording.

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?

For a destructive mutation with an output schema and existing annotations, this description covers the important missing context: permanence, default dry-run behavior, user approval, and the safer alternative. No critical agent decision information is omitted.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains dryRun thoroughly, including its default and approval workflow, though it does not add detail about automationId beyond the field name and UUID 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?

The description starts with a specific verb and resource: permanently delete an automation. It also distinguishes the destructive delete from the safer alternative of using set_automation_active to stop the automation.

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?

It gives explicit usage guidance: dry run is the default, actual deletion requires a second call with dryRun=false after user approval. It also names the alternative for merely stopping the automation and states the condition for choosing it.

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