Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

n8n: Activate workflow

n8n_activate_workflow
Destructive

Activate a workflow so it runs automatically when triggered. Requires a workflow that already has at least one trigger node.

Instructions

[UNIFIED] Activate a workflow so it runs automatically when triggered. Workflow must have at least one trigger node.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
workflow_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation profile is covered. The description adds the trigger-node prerequisite and the runtime effect of activation, but omits what happens when the workflow is already active, whether permissions or project scope matter, and any side effects on scheduling.

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?

Two short sentences, zero filler, with the purpose front-loaded and the constraint immediately after. Nothing is repeated from the title or annotations.

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

Completeness3/5

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

For a two-parameter state-changing tool with no output schema, the description covers the core action and the main failure condition. It is still incomplete on parameter meaning (site) and on post-call behavior, which matter for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for the two required parameters — and it explains neither. workflow_id is inferable from its name, but site is not clarified at all (multi-instance selector? project? host?), leaving a real ambiguity for the agent.

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?

States a specific verb+resource ("Activate a workflow") plus the concrete effect ("runs automatically when triggered"), which cleanly separates it from n8n_deactivate_workflow. It stops short of naming any sibling explicitly, so it is clear but not maximally differentiated.

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

Usage Guidelines3/5

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

Gives one real precondition — the workflow must have at least one trigger node — which tells the agent when the call will fail. It offers no guidance on when to activate versus execute/duplicate, and no note on what to do if the workflow is already active.

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