Modify an existing n8n workflow node by changing its name, position, parameters, credentials, or disabled status.
Update an existing node in a workflow
| Name | Required | Description | Default |
|---|---|---|---|
| nodeId | Yes | The node ID to update | |
| updates | Yes | Node updates to apply | |
| workflowId | Yes | The workflow ID |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a mutation ('update') but does not explain partial-update semantics, required permissions, reversibility, or side effects.
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?
The description is a single, front-loaded sentence with no wasted words. It is appropriately concise, though its brevity leaves gaps that other dimensions measure.
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?
The schema is rich with full parameter coverage and nested object details, which compensates for the sparse description on parameter semantics. However, for a mutation tool with no annotations and no output schema, the lack of behavioral context (e.g., partial updates, error conditions) leaves it only minimally complete.
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%, so the schema already documents all parameters, including nested update fields. The description adds no additional meaning beyond what the schema provides, yielding the baseline score of 3.
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?
The description states a clear verb+resource: 'Update an existing node in a workflow.' It implicitly contrasts with create_node/delete_node via the verb 'update,' but does not explicitly name or differentiate from siblings.
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?
There is no guidance on when to use this tool versus alternatives like create_node or delete_node. The only implied usage is that it applies to existing nodes, which is minimal context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.