n8n - 💡(How to fix) Fix Bug Report: update_workflow MCP tool requires undocumented 'operations' field

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

When calling update_workflow via MCP with the documented parameters (code + workflowId), the server returns the following error: MCP error -32602: Input validation error: Invalid arguments for tool update_workflow: 3. Observe the error above

RAW_BUFFERClick to expand / collapse

Hi n8n Support,

I'd like to report a bug with the MCP server's update_workflow tool.

Environment: n8n Cloud (bbrown.app.n8n.cloud)

Issue: When calling update_workflow via MCP with the documented parameters (code + workflowId), the server returns the following error:

MCP error -32602: Input validation error: Invalid arguments for tool update_workflow: [ { "code": "invalid_type", "expected": "array", "received": "undefined", "path": ["operations"], "message": "Required" } ]

The tool schema exposed to MCP clients defines only these parameters:

  • code (required)
  • workflowId (required)
  • description (optional)
  • name (optional)

However, the server internally requires an additional field called 'operations' (expected type: array) that is not documented in the tool schema and cannot be passed by MCP clients.

This makes update_workflow completely unusable via MCP.

Steps to reproduce:

  1. Connect to n8n MCP server
  2. Call update_workflow with valid 'code' (validated via validate_workflow) and a valid 'workflowId'
  3. Observe the error above

Expected behavior: The workflow is updated successfully. Actual behavior: Server rejects the call due to a missing undocumented required field.

Please either expose 'operations' in the tool schema, or remove the internal requirement for it.

Thanks, Ben Brown

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING