Skip to main content
Glama
czlonkowski

n8n-MCP

by czlonkowski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

n8n_autofix_workflow

Idempotent

Automatically detect and fix common n8n workflow validation errors. Preview proposed fixes or apply them directly to resolve expression format, typeVersion, webhook path, and connection structure issues.

Instructions

Automatically fix common workflow validation errors. Preview fixes or apply them. Fixes expression format, typeVersion, error output config, webhook paths, connection structure issues (numeric keys, invalid types, ID-to-name, duplicates, out-of-bounds indices).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWorkflow ID to fix
fixTypesNoTypes of fixes to apply (default: all)
maxFixesNoMaximum number of fixes to apply (default: 50)
applyFixesNoApply fixes to workflow (default: false - preview mode)
confidenceThresholdNoMinimum confidence level for fixes (default: medium)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.66.2
  2. Removedv2.65.1
  3. Addedv2.56.0
  4. Removedv2.55.0
  5. Changed1 schema field changedv2.48.3
    • changedInput schema / properties / fixTypes / items / enum
      Previous value: -[
-  "expression-format",
-  "typeversion-correction",
-  "error-output-config",
-  "node-type-correction",
-  "webhook-missing-path",
-  "typeversion-upgrade",
-  "version-migration"
-]New value: +[
+  "expression-format",
+  "typeversion-correction",
+  "error-output-config",
+  "node-type-correction",
+  "webhook-missing-path",
+  "typeversion-upgrade",
+  "version-migration",
+  "tool-variant-correction",
+  "connection-numeric-keys",
+  "connection-invalid-type",
+  "connection-id-to-name",
+  "connection-duplicate-removal",
+  "connection-input-index"
+]
  6. Addedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations indicate idempotentHint=true and destructiveHint=false, consistent with a non-destructive fixer. The description adds that fixes can be previewed or applied, and lists specific issue types. No contradictions.

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?

The description is concise, front-loading the action and purpose in a single short paragraph. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers what the tool does and lists fix types, but does not describe the output format or return value. Given no output schema, this is a gap for agents needing to parse results.

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%, so baseline 3. The description lists fixTypes but does not add significant meaning beyond the enum values. Parameters are adequately described in the schema.

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?

The description clearly states the tool automatically fixes common workflow validation errors, with explicit examples of fix types (expression format, typeVersion, etc.). It distinguishes from sibling tools like validate_workflow by mentioning both preview and apply modes.

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?

The description implies usage for fixing validation errors but does not provide explicit when-to-use vs when-not-to-use guidance or compare with alternatives like manual updates via n8n_update_*. No exclusions mentioned.

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