Skip to main content
Glama

duplicate_automation

Copy an automation, settings and all, as a new PAUSED one named " (copy)".

Paused on purpose: an identical active twin would DM every trigger twice (Instagram allows one private reply per comment, so one of them fails), and copying would otherwise walk past the plan's active-automation limit. Review the copy with get_automation, change what should differ with update_automation, then activate it with update_automation(status="active"), which re-runs the conflict and plan checks. Counters start at zero.

Needs the automations permission.

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": "duplicate_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes
automation_idYes

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.3/5.0
Behavior5/5

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

Annotations only give the generic mutation profile (readOnly=false, destructive=false, idempotent=false); the description adds substantial context beyond that: the copy is deliberately PAUSED, why activation is deferred (duplicate DMs, one-private-reply-per-comment limit), that the plan's active-automation limit would otherwise be bypassed, that activation re-runs conflict and plan checks, and that counters start at zero. It also names the required automations permission. Nothing contradicts the annotations.

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 outcome and naming are front-loaded in the first sentence, then the rationale follows. The Instagram private-reply parenthetical is somewhat verbose, but every passage carries real decision-relevant information, so nothing is clearly wasteful.

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 two-parameter mutation tool with an output schema (so return values need not be described), the definition covers state of the result, permission requirements, plan/conflict implications, and the full post-copy workflow. An agent has everything needed to call it and to know what happens next.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two required parameters, and the description never mentions workspace_id or automation_id — it only implies that the unnamed target is what gets copied. With zero schema documentation, the description needed to compensate for the missing parameter meaning and does not.

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?

"Copy an automation, settings and all, as a new PAUSED one named '<name> (copy)'" specifies the verb (copy), the resource (automation), the scope (settings included), and the resulting state and naming convention. That distinguishes it implicitly from create_automation and get_automation without ambiguity.

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?

The description lays out an explicit follow-up sequence: review with get_automation, edit with update_automation, then activate via update_automation(status="active"). It gives clear context and next steps but never states the condition that selects duplicate_automation over create_automation, so it stops short of full when/when-not guidance.

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