Skip to main content
Glama
ellmos-ai

n8n-manager-mcp

by ellmos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

n8n_create_workflow

Create a new n8n workflow by supplying workflow JSON with nodes and connections. Defines node positions and parameters, optionally activates the workflow after creation.

Instructions

Create a new n8n workflow. Provide the full workflow JSON including nodes and connections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWorkflow name
nodesYesArray of workflow nodes
activateNoActivate workflow after creation
connectionsNoArray of connections between nodes
server_nameNoServer name. Uses default if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.17
    • addedInput schema / properties / connections / items / properties / from_output / description
      Added value: +"Source output index (integer 0-1000)"
    • addedInput schema / properties / connections / items / properties / from_output / maximum
      Added value: +1000
    • addedInput schema / properties / connections / items / properties / from_output / minimum
      Added value: +0
    • changedInput schema / properties / connections / items / properties / from_output / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / connections / items / properties / to_input / $ref
      Added value: +"#/properties/connections/items/properties/from_output"
    • addedInput schema / properties / connections / items / properties / to_input / description
      Added value: +"Target input index (integer 0-1000)"
    • removedInput schema / properties / connections / items / properties / to_input / type
      Removed value: -"number"
  2. First observedv0.1.6

TDQS

C2.9/5.0
Behavior2/5

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

There are no annotations, so the description carries the burden of disclosing side effects. It only says 'Create' and does not mention duplicate handling, activation behavior, server selection, or reversibility. The schema's activate default is not reflected in the prose, and no return behavior is described.

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

Conciseness4/5

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

The description is a single short sentence with no filler, and it front-loads the core action. The second phrase about 'full workflow JSON' is somewhat redundant given the schema, but the overall structure is clean and scannable.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is thin: it omits expected return value, duplicate-name behavior, and relationship to import/update siblings. The detailed schema mitigates parameter confusion but cannot fully compensate for missing behavioral and usage context.

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 description coverage is 100%, so the schema already documents all five parameters. The prose adds only a general hint that nodes and connections are needed for a complete workflow, which is mildly helpful but does not substantially extend what the schema already provides.

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

Purpose4/5

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

The description states a clear action and resource: 'Create a new n8n workflow.' It is specific and unambiguous about the core operation. However, it does not distinguish itself from sibling n8n_import_workflow, which also creates workflows via import, so it stops short of a 5.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives such as n8n_import_workflow or n8n_update_workflow. The description only states what the tool does, leaving the agent to infer which workflow-creation path is appropriate.

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