Skip to main content
Glama

update_automation

Idempotent

Edit an automation. Omit anything you don't want to change.

Setting any one of trigger_type/post_target/post_ids/keywords/ keyword_match merges it onto the automation's existing trigger rather than replacing the whole thing — changing just post_ids to add one more reel doesn't reset trigger_type or keywords back to defaults. Same for ai_goal/ai_context/ai_exit_condition/ai_tone/ai_link against the existing ai config.

Setting public_reply_messages/private_dm_messages merges onto the existing action list the same way the trigger/ai fields above do — editing just the DM text keeps the public-reply messages and every button on the DM card (links, PDF, carousel) exactly as they were; you don't need to pass them again to keep them.

dm_link_button_url merges onto the private_dm action the same way: set it (https://...) to turn the DM into a tappable link-button card instead of plain text, or pass "" to remove the button and go back to plain text. Don't leave the URL typed into private_dm_messages as well when using this.

dm_buttons replaces the WHOLE button list on the DM card in one go — pass it when the automation needs more than a single link, a PDF button, or a product carousel (see create_automation for the shape). Pass [] to strip every button. Omitting dm_buttons (even while setting private_dm_messages) leaves the existing buttons untouched.

dm_link_button_label sets the button's visible text, under the same rule as create_automation: pass it only when the user has told you the exact wording, never something you derived from the link itself. Leave it unset and a button being added for the first time reads "Click here", while an existing button keeps the label it already has.

follow_up_enabled/follow_up_delay_seconds/follow_up_message edit the second "did you get it?" DM (see create_automation for the limits) and merge onto the existing follow-up the same way — pass follow_up_enabled= false to turn it off while keeping its text for later.

status="active" re-runs every plan/conflict check this automation's current config would need, so re-activating a grandfathered or since-conflicting automation can still fail — relay the message. create_automation leaves a new automation paused, and this is how it goes live. Switching it on needs user_confirmed=true.

user_confirmed: required (true) whenever status="active". Set to true only after the user has seen the automation's trigger, targeting and message text and said yes. Not needed for status="paused" or for other edits.

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": {
      "workspace_id": "<workspace_id>",
      "automation_id": "<automation_id>"
    },
    "name": "update_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
statusNo
ai_goalNo
ai_linkNo
ai_toneNo
keywordsNo
post_idsNo
ai_contextNo
dm_buttonsNo
post_targetNo
ice_breakersNo
trigger_typeNo
workspace_idYes
automation_idYes
keyword_matchNo
ask_for_followNo
user_confirmedNo
ai_exit_conditionNo
follow_up_enabledNo
follow_up_messageNo
dm_link_button_urlNo
follow_gate_messageNo
ice_breaker_repliesNo
private_dm_messagesNo
dm_link_button_labelNo
public_reply_messagesNo
follow_up_delay_secondsNo

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
statsNoWhat happened after this automation ran. `dms_failed` is a send that was tried and did not land (dead token, Meta rate limit, policy rejection) — read it next to `events_received` before concluding an automation 'works'.
statusYes
ai_goalYes
ai_linkYes
ai_toneYes
stalledNo
dms_sentYes
keywordsYes
post_idsYes
ai_contextYes
dm_buttonsNo
post_targetYes
ice_breakersYes
trigger_typeYes
keyword_matchYes
ask_for_followYes
ai_exit_conditionYes
follow_up_enabledNo
follow_up_messageNo
dm_link_button_urlYes
follow_gate_messageYes
ice_breaker_repliesNo
private_dm_messagesYes
public_replies_sentYes
dm_link_button_labelYes
public_reply_messagesYes
follow_up_delay_secondsNo
ice_breakers_sync_errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With annotations only declaring readOnly=false/destructive=false/idempotent=true, the description carries real weight: it discloses merge-vs-replace semantics per field group, that dm_buttons replaces the entire list while omission preserves it, that status='active' re-runs plan/conflict checks and can still fail, and that follow_up_enabled=false disables while retaining text. This is exactly the non-obvious behavior an agent cannot get from annotations.

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

Conciseness3/5

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

The lead sentence is front-loaded and paragraphs are grouped by concern, which helps with 27 parameters. However, the merge-semantics explanation is restated three or four times ('merges onto the ... the same way'), and the prose runs long enough that an agent could lose the replace-vs-merge distinction buried mid-paragraph.

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 27-parameter, high-blast-radius update tool with an output schema present, the definition covers the consequential semantics: partial updates, list replacement, activation gating and confirmation. A handful of parameters and their interaction (ice breakers, follow gate, ask_for_follow) are unaddressed, which is the main remaining gap.

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% across 27 parameters, so the description must compensate, and it does for the highest-risk ones: trigger fields, ai_* fields, message lists, dm_link_button_url (including '' to remove), dm_link_button_label defaulting rules, follow-up fields, status and user_confirmed. It leaves some parameters unexplained (name, ice_breakers, ice_breaker_replies, ask_for_follow, follow_gate_message), so it is strong but not complete.

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?

Opens with a specific verb+resource ('Edit an automation') and immediately states the partial-update contract ('Omit anything you don't want to change'). It differentiates from create_automation by noting new automations start paused and this is how they go live. It does not distinguish itself from other siblings like duplicate_automation, but the purpose is unambiguous.

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 explicit when-to-set guidance for each field cluster (set dm_buttons for multi-button cards, pass [] to strip, omit to leave untouched) and an explicit when-required rule for status='active' plus user_confirmed=true. Lacks any mention of alternative tools to use instead, e.g. when to use preview_automation before activating, so it stops short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources