Skip to main content
Glama
ifmelate

n8n-workflow-builder-mcp

by ifmelate

add_node

Add a new node to an existing n8n workflow, defining its type, position, parameters, and name. Specify workflow details and optional webhook ID or path for precise integration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_nameNoThe name for the new node (e.g., 'My Gmail Node')
node_typeYesThe type of node to add (e.g., 'gmail', 'slack', 'openAi'). You can specify with or without the 'n8n-nodes-base.' prefix. The system will handle proper casing (e.g., 'openai' will be converted to 'openAi' if that's the correct casing).
parametersNoThe parameters for the node
positionNoThe position of the node {x,y} - will be converted to [x,y] for N8nWorkflowNode
typeVersionNoThe type version for the node (e.g., 1, 1.1). Defaults to 1 if not specified.
webhookIdNoOptional webhook ID for certain node types like triggers.
workflow_nameYesThe Name of the workflow to add the node to
workflow_pathNoOptional direct path to the workflow file (absolute or relative to current working directory). If not provided, uses standard workflow_data directory approach.
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ifmelate/n8n-workflow-builder-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server