Create a backup snapshot of an n8n workflow before making changes. Provide a workflow ID and an optional description to preserve the current state for safe rollback.
Create a backup snapshot of a workflow before making changes
| Name | Required | Description | Default |
|---|---|---|---|
| workflowId | Yes | Workflow ID to backup | |
| description | No | Optional description for this backup (e.g., "Before AI optimization") |
Changes observed during successful MCP inspections.
v2.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It states that a backup snapshot is created but does not disclose whether the workflow itself is modified, whether repeated calls create multiple snapshots, how long backups are retained, or what response is returned.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with the action front-loaded and zero filler. Every word contributes to the core meaning and intended usage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter tool with 100% schema coverage, this is minimally adequate for making the call. However, with no annotations and no output schema, the missing side-effect and return information leaves an agent unsure how to confirm the backup or reference it later when listing or restoring.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and both workflowId and description have adequate schema-level explanations. The description adds no parameter-specific detail beyond what the schema already provides, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Create a backup snapshot of a workflow'. The qualifier 'before making changes' clearly fixes its role and helps distinguish it from siblings like list_workflow_backups and restore_workflow.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly ties usage to a trigger: use this before making changes to a workflow. It does not name alternatives or exclusions, but the intended moment of use is unambiguous, making it easy for an agent to select.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.