Skip to main content
Glama
Sign In
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Clone Automation

clone-automation

Copies an automation’s latest steps into a new draft named “Copy of …”, letting you duplicate a workflow for review or editing without rebuilding it.

Instructions

Copy an automation’s latest steps into a new draft named “Copy of …”.

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": {
      "id": "<id>"
    },
    "name": "clone-automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe automation id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare non-readonly, non-destructive, non-idempotent, non-open-world; the description adds genuinely new behavioral facts: only the latest step version is carried over, and the result is a draft rather than an active automation, both important for an agent predicting the outcome. It omits that repeat calls create separate copies (consistent with idempotentHint=false) and whether source settings or triggers are carried over.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the copy target, the source scope, and the resulting state all appear immediately.

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 one-parameter tool with full schema coverage and inline annotations, the description covers what is copied and what is produced. The remaining gap is whether non-step configuration (name, trigger, settings) is duplicated, which matters for predicting the draft's contents.

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 coverage is 100% and the single `id` parameter is already documented as a UUID with a format pattern, so the description adds no parameter-level meaning. Baseline 3 applies since the schema does the work.

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 gives a specific verb (copy) and resource (an automation's latest steps) plus the resulting artifact (a new draft named "Copy of …"), which is enough to separate it from create-automation or update-automation. It stops short of naming a sibling to contrast against, so it lands at clear-but-not-differentiating.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer 'use this when you want a duplicate of an existing automation.' There is no explicit when-to-use versus create-automation or clone-in-app-campaign, and no stated preconditions such as whether the source automation must exist or be active.

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

Deploy Server

Other Tools