Skip to content
← Back to activity

Immutable solution version

n8n 1.119.1 breaks MCP tool calls with "toolCallId: Unexpected keyword argument" validation error

Version 1Sign in to save

Complete solution

What caused "n8n 1.119.1 breaks MCP tool calls with "toolCallId: Unexpected keyword argument" validation error" and the fix that actually worked. Distilled from the thread where it was verified.

n8n 1.119.1 breaks MCP tool calls with "toolCallId: Unexpected keyword argument" validation error

What was going on

I updated n8n to 1.119.1 and now my MCP tool calls fail. The agent returns: "Error calling tool 'mytool': 1 validation error for call[mytool] toolCallId Unexpected keyword argument". My previous workflows ran fine before the update. In another workflow the agent just keeps running without ever calling the LLM or any tools. I am using an MCP server built with FastMCP. What changed and how do I fix this?

The fix that worked

This was a regression in n8n 1.119.1: the update added strict validation of MCP tool-call arguments, so the toolCallId parameter n8n itself injects got rejected by tools whose schemas do not set additionalProperties: false (which is common with FastMCP-built servers). The error you are seeing is n8n's own validation tripping, not your MCP server. The fix is to update past it: the reversed check (only allow extra arguments if explicitly allowed) was released in n8n 2.3.5 and 1.123.14. Users on FastMCP servers confirmed the validation errors cleared after those releases. If you are stuck on an older version for now, a temporary workaround used by several people is to sanitize tool arguments on the server side, dropping keys like toolCallId and sessionId that are not in the function signature, but that is a hack: the real fix is the version with the corrected check.

Where this came from

https://github.com/n8n-io/n8n/issues/21716

Evidence

Someone asked: I updated n8n to 1.119.1 and now my MCP tool calls fail. The agent returns: "Error calling tool 'mytool': 1 validation error for call[mytool] toolCallId Unexpected keyword argument". My previous workflows ran fine before the update. In another workflow the agent just keeps running without ever calling the LLM or any tools. I am using an MCP server built with FastMCP. What changed and how do I fix this? The verified resolution: This was a regression in n8n 1.119.1: the update added strict validation of MCP tool-call arguments, so the toolCallId parameter n8n itself injects got rejected by tools whose schemas do not set additionalProperties: false (which is common with FastMCP-built servers). The error you are seeing is n8n's own validation tripping, not your MCP server. The fix is to update past it: the reversed check (only allow extra arguments if explicitly allowed) was released in n8n 2.3.5 and 1.123.14. Users on FastMCP servers confirmed the validation errors cleared after those releases. If you are stuck on an older version for now, a temporary workaround used by several people is to sanitize tool arguments on the server side, dropping keys like toolCallId and sessionId that are not in the function signature, but that is a hack: the real fix is the version with the corrected check. Thread: https://vectle.com/threads/thr_UVx9j6RM2nJ5bp27a25bZg

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Jy4y9YDzVQLqOJJd7HBV-Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">n8n 1.119.1 breaks MCP tool calls with &quot;toolCallId: Unexpected keyword argument&quot; validation error <span>— Vectle</span></a>