uplika

Replace an automation's flow

put_automation

Destructive

Replace an automation's whole document. Pass the version you got from get_automation; a stale version is refused with version_conflict so a concurrent edit is not overwritten. Node types: send (mode window | private_reply | public_reply), condition, action, delay, random, goto, ai. Waiting is a send node with buttons and next: null; the tapped button's next continues. A loop must pass through such a wait. Validation problems come back with paths. Changing a live flow changes what goes out to people.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`doc`	Yes	One automation flow. triggers start it, nodes are the steps, start names the first node. Waiting is not a node: a send node with buttons and next: null waits for the person to tap one, and that button's next continues. A loop must pass through such a wait.
`name`	No
`version`	Yes
`workspaceId`	No	Which workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 21, 2026

addedInput schema / properties / doc / properties / nodes / additionalProperties / properties / items / items / properties / message
```
Added value: +{
+  "description": "follow: message on the mutual request.",
+  "type": "string"
+}
```
addedInput schema / properties / doc / properties / nodes / additionalProperties / properties / items / items / properties / mutual
```
Added value: +{
+  "description": "follow: ask for a mutual neighbor relation (Naver). Default false.",
+  "type": "boolean"
+}
```

changed

Input schema / properties / doc / properties / nodes / additionalProperties / properties / items / items / properties / type / enum

Previous value: -[
-  "add_tag",
-  "remove_tag",
-  "set_field",
-  "clear_field",
-  "opt_in",
-  "opt_out",
-  "open_conversation",
-  "close_conversation",
-  "assign",
-  "hide_reply",
-  "approve_reply"
-]New value: +[
+  "add_tag",
+  "remove_tag",
+  "set_field",
+  "clear_field",
+  "opt_in",
+  "opt_out",
+  "open_conversation",
+  "close_conversation",
+  "assign",
+  "hide_reply",
+  "approve_reply",
+  "follow"
+]

Changed6 schema fields changedSep 20, 2026

changed

Input schema / properties / doc / properties / nodes / additionalProperties / properties / all / items / properties / field / enum

Previous value: -[
-  "tag",
-  "follows_us",
-  "we_follow",
-  "follower_count",
-  "verified",
-  "window_open",
-  "opted_in",
-  "last_interaction_hours",
-  "field",
-  "intent",
-  "sentiment",
-  "text"
-]New value: +[
+  "tag",
+  "follows_us",
+  "we_follow",
+  "follower_count",
+  "verified",
+  "window_open",
+  "opted_in",
+  "last_interaction_hours",
+  "field",
+  "intent",
+  "sentiment",
+  "text",
+  "clicked"
+]

addedInput schema / properties / doc / properties / nodes / additionalProperties / properties / field

Added value: +{
+  "description": "ask: contact field the answer is stored in (e.g. email).",
+  "type": "string"
+}

addedInput schema / properties / doc / properties / nodes / additionalProperties / properties / maxTries

Added value: +{
+  "description": "ask: default 3. After that the flow continues without a value.",
+  "type": "integer"
+}

addedInput schema / properties / doc / properties / nodes / additionalProperties / properties / retry
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / properties / doc / properties / nodes / additionalProperties / properties / type / enum

Previous value: -[
-  "send",
-  "condition",
-  "action",
-  "delay",
-  "random",
-  "goto",
-  "ai"
-]New value: +[
+  "send",
+  "condition",
+  "action",
+  "delay",
+  "random",
+  "goto",
+  "ai",
+  "ask"
+]

addedInput schema / properties / doc / properties / nodes / additionalProperties / properties / validate

Added value: +{
+  "description": "ask: how to check the answer. Wrong answers get `retry`, up to maxTries.",
+  "enum": [
+    "email",
+    "none"
+  ],
+  "type": "string"
+}

AddedSep 20, 2026
RemovedSep 20, 2026
AddedSep 20, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false. The description adds context about version conflict behavior, validation paths, and that changing a live flow affects people. It does not contradict the annotations and provides meaningful behavioral detail beyond the flags.

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?

The description is dense and logically ordered: purpose, version requirement, node types, waiting semantics, validation, and impact. Every sentence adds value, though it is somewhat long. It is well structured and front-loaded with the core purpose.

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?

For a complex tool with a large schema, the description covers the essential usage nuances: versioning, node types, waiting/loop rules, and validation behavior. It does not describe return values, but there is no output schema, so that is acceptable. It is sufficient for an agent to call the tool correctly.

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 description coverage is 40%, so the description must compensate. It clarifies the version parameter and explains the doc structure (node types, waiting, loops). However, it does not elaborate on id, name, or workspaceId, leaving gaps that the schema only partially fills.

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?

The description states a clear action: 'Replace an automation's whole document.' This is a specific verb and resource. It distinguishes from partial updates and creation implicitly, but does not explicitly name alternative tools like create_automation, so it misses the top score.

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?

Provides a concrete usage rule: 'Pass the version you got from get_automation; a stale version is refused with version_conflict.' This guides when to use it and how to avoid conflicts. It does not explicitly state when not to use it (e.g., for creation), but the instruction is actionable.

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

All uplika 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?