Skip to main content
Glama
Sign In
n8n MCP Server

n8n MCP Server

by verzth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create n8n Workflow

n8n_create_workflow

Create a new n8n workflow by providing name, nodes, connections, and optional settings. Receive the new workflow ID for immediate use.

Instructions

Create a new workflow in n8n.

Args:

  • name (string): Workflow name

  • nodes (array): Array of node objects (n8n node definitions)

  • connections (object): Node connection map

  • settings (object?): Workflow settings

  • active (boolean): Whether to activate immediately (default false)

Returns: Created workflow with its ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "nodes": "<nodes>",
      "connections": "<connections>"
    },
    "name": "n8n_create_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesWorkflow name
nodesYesArray of n8n node definitions
activeNoActivate immediately after creation
settingsNoWorkflow settings
connectionsYesNode connection map

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already classify the tool as a non-read-only, non-idempotent mutation. The description adds context by documenting the 'active' parameter's default behavior and stating the return value (created workflow with ID). It does not contradict annotations and provides additional useful behavioral details.

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 compact, well-organized with a labeled arg list, and includes a returns line. Every sentence is useful, with no redundancy or filler.

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

Completeness4/5

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

For a 5-parameter tool with nested objects and no output schema, the description covers the essentials—inputs and return value. It doesn't detail the required format for n8n node definitions or connection maps, but given the schema and annotations, the description is sufficiently complete for correct invocation.

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 the baseline is 3. The description repeats parameter names and basic types but adds little beyond the schema (e.g., marking settings as optional and restating the default for active). It does not explain the structure of nodes or connections, which would be more valuable.

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 states 'Create a new workflow in n8n' with a clear verb and resource. It distinguishes from sibling tools like update/delete/activate workflows by specifying the creation intent. The arg list further clarifies the operation.

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

Usage Guidelines4/5

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

The description makes it clear this is for creating workflows, and the context is unambiguous. It does not explicitly list when not to use it or point to alternatives, but the purpose is self-evident, giving clear context without exclusions.

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