Skip to main content
Glama

uplika

by com.uplika
OverviewDiscussionsAdmin

Edit an automation (replace its flow)

put_automation
Destructive

Edit an automation by replacing its whole document: for flows no template covers, or that were already edited on the canvas. If get_automation shows templateParams, change it with update_automation instead (only the params you pass change; an Instagram follow check is requireFollow, notFollowingMessage and recheckTitle). Replacing the document of a flow that still has its template form is refused with automation_is_template, because the person can no longer open it in the form afterwards; pass detachTemplate: true only when the change cannot be expressed as template params. Read it first with get_automation and pass the version you got; 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. A comment trigger's post.postId takes the post's link too; the server resolves it to the uplika post id. Validation problems come back with paths. Changing a live flow changes what goes out to people.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
docYesOne 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.
nameNo
versionYes
workspaceIdNoWhich 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.
detachTemplateNoOnly for a flow that still has its template form: true turns it into a canvas-only flow the form can no longer open. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / doc / properties / triggers / items / properties / post / description
      Previous value: -"comment triggers: { postId } | \"any\" | \"next\". \"next\" binds to the next post you publish."New value: +"comment triggers: { postId } | \"any\" | \"next\". postId may also be the post's link (the server resolves it to the uplika post id when saving). \"next\" binds to the next post you publish."
  2. Changed1 schema field changed
    • addedInput schema / properties / doc / properties / triggers / items / properties / publicReplyAi
      Added value: +{
+  "description": "Instead of publicReply: the AI writes the public reply for each comment, after the flow ran. Told a DM was sent only when the private reply went out.",
+  "properties": {
+    "instruction": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "instruction"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / detachTemplate
      Added value: +{
+  "description": "Only for a flow that still has its template form: true turns it into a canvas-only flow the form can no longer open. Default false.",
+  "type": "boolean"
+}
  4. Changed4 schema fields changed
    • changedInput schema / properties / doc / properties / nodes / additionalProperties / properties / mode / description
      Previous value: -"send: window = inside the 24-hour window, private_reply = one DM to a commenter, public_reply = comment under the post."New value: +"send: window = inside the 24-hour window, private_reply = one DM to a commenter, public_reply = comment under the post. ai: window | public_reply | post_comment (post_comment = read the neighbor's post that triggered the flow and leave one comment; neighbor_post trigger only)."
    • changedInput schema / properties / doc / properties / nodes / additionalProperties / properties / mode / enum
      Previous value: -[
-  "window",
-  "private_reply",
-  "public_reply"
-]New value: +[
+  "window",
+  "private_reply",
+  "public_reply",
+  "post_comment"
+]
    • changedInput schema / properties / doc / properties / triggers / items / properties / kind / enum
      Previous value: -[
-  "comment",
-  "live_comment",
-  "message",
-  "story_reply",
-  "story_mention",
-  "referral",
-  "mention",
-  "contact_created",
-  "tag_added",
-  "tag_removed",
-  "field_changed",
-  "schedule"
-]New value: +[
+  "comment",
+  "live_comment",
+  "message",
+  "story_reply",
+  "story_mention",
+  "referral",
+  "mention",
+  "neighbor_post",
+  "contact_created",
+  "tag_added",
+  "tag_removed",
+  "field_changed",
+  "schedule"
+]
    • addedInput schema / properties / doc / properties / triggers / items / properties / neighbors
      Added value: +{
+  "description": "neighbor_post trigger (Naver Blog): mutual = only mutual neighbors (default), all = every neighbor in the feed.",
+  "enum": [
+    "mutual",
+    "all"
+  ],
+  "type": "string"
+}
  5. Changed1 schema field changed
    • changedInput 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",
-  "follow"
-]New value: +[
+  "add_tag",
+  "remove_tag",
+  "set_field",
+  "clear_field",
+  "opt_in",
+  "opt_out",
+  "open_conversation",
+  "close_conversation",
+  "assign",
+  "hide_reply",
+  "approve_reply",
+  "follow",
+  "like_comment"
+]
  6. Changed3 schema fields changed
    • 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"
+}
    • changedInput 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"
+]
  7. Changed6 schema fields changed
    • changedInput 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"
+}
  8. Added
  9. Removed
  10. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true; the description goes well beyond that by naming the specific refusal errors (automation_is_template, version_conflict), explaining the concurrency guarantee (a stale version will not overwrite a concurrent edit), noting that validation failures return paths, and warning that editing a live flow changes what goes out to people.

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-loads purpose and the update_automation alternative before diving into node/loop semantics, so the important routing decision survives skimming. It is dense and long, with a parenthetical node-type list and the wait/loop rule repeated from the doc field's schema description, which costs some efficiency.

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 tool whose doc parameter is a deeply nested object schema with no output schema, the description covers the failure modes an agent must anticipate, the versioning contract, and the structural rules the schema cannot express (loops must pass through a wait, button next: null semantics). What remains thin is the trigger/document construction detail, though the schema largely handles that.

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?

With 50% schema coverage across six parameters, the description carries real weight: it explains version semantics (stale versions rejected), the meaning and risk of detachTemplate, and how doc semantics work (node types, wait-as-send-node, comment postId accepting a link). Some of the node-type and wait content duplicates enums already present in the schema, so it is not purely additive.

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 and resource with its exact semantics: 'Edit an automation by replacing its whole document.' It further scopes which flows this applies to (flows no template covers or already edited on canvas), which cleanly separates it from create_automation and update_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?

Explicit routing: if get_automation shows templateParams, use update_automation instead; use detachTemplate only when the change cannot be expressed as template params. It also mandates the read-then-write workflow by requiring the version from get_automation, so the agent knows exactly when and how to invoke this.

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

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