Arara MCP

Official

Overview Schema Source Related Servers Discussions Admin

set_automation_active

DestructiveIdempotent

Activate or deactivate a WhatsApp automation; activation defaults to a dry run showing flow and per-run cost for approval, while deactivation stops new runs immediately.

Instructions

Turn an automation on or off. Turning ON makes real, paid WhatsApp messages go out to customers on every trigger, so with active=true it is a dry run by default: it returns the flow and the cost per run for the user to approve, and only activates when called again with dryRun=false. Turning off (active=false) applies immediately and only stops new runs. The plan limits how many automations can be active.

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>",
      "active": "<active>"
    },
    "name": "set_automation_active"
  }
}

Input Schema

Name	Required	Description	Default
`active`	Yes
`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.3/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the real-world cost consequence (paid WhatsApp messages to customers on every trigger), the two-step approval flow that makes the default safe, that deactivation only stops new runs, and that plan limits cap active automations. These are exactly the facts an agent needs before invoking a destructiveHint, openWorld tool and are not derivable from the structured fields.

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?

Front-loaded with the purpose, then layered risk, then mechanics. All four sentences carry information, though the closing sentence about plan limits states the constraint without saying what happens when it is exceeded, making it the weakest of the set.

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?

An output schema exists, so return values need not be explained, yet the description still previews the useful shape (flow and cost per run) for the dry-run path. Combined with the mutation semantics, reversibility scope, and billing risk, it is complete for a three-parameter state-changing tool.

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 the parameter burden, and it does for the two consequential ones: it explains the semantics of active in both directions and, critically, that dryRun defaults to true and must be set false to actually activate. automationId is not described, but its meaning is self-evident from the tool's purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Turn an automation on or off') and immediately defines what each direction means. It does not explicitly distinguish itself from the closest sibling, update_automation, which an agent could plausibly confuse with a toggle operation.

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

Usage Guidelines4/5

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

Gives concrete when-to guidance: active=true is a dry run by default and requires a second call with dryRun=false to actually activate, while active=false applies immediately. No sibling alternatives are named, so an agent comparing against update_automation or delete_automation gets no routing help.

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