Skip to main content
Glama
Sign In
n8n MCP Server

n8n MCP Server

by verzth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Activate n8n Workflow

n8n_activate_workflow
Idempotent

Activate a workflow to enable automatic execution on triggers or schedules.

Instructions

Activate (publish) a workflow so it runs automatically on triggers/schedules.

Args:

  • id (string): Workflow ID to activate

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": {
      "id": "<id>"
    },
    "name": "n8n_activate_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWorkflow ID to activate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already indicate readOnly=false and idempotentHint=true; the description adds the behavioral consequence 'runs automatically on triggers/schedules.' However, it doesn't disclose potential side effects like validation errors or scheduling behavior beyond the basics, so it provides moderate added context beyond annotations.

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 front-loaded with a clear, concise first sentence and a minimal args list. Every word adds value; no wasted text.

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

Completeness5/5

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

For a single-parameter, no-output-schema tool with adequate annotations, this description is fully sufficient. It states the action, the effect, and the required argument, leaving no significant gaps.

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% and the description merely repeats the parameter description ('Workflow ID to activate') without adding new semantics. Since the schema already fully documents the only parameter, the baseline of 3 is appropriate.

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 uses a specific verb ('Activate') and resource ('workflow') and clarifies the effect: 'runs automatically on triggers/schedules.' This clearly distinguishes it from siblings like n8n_deactivate_workflow or n8n_update_workflow.

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 gives clear context: activation is for publishing a workflow so it runs automatically. It does not explicitly name alternatives or exclusion criteria, but the use case is unambiguous and implicitly contrasts with deactivating.

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