Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

Activate n8n Workflow

n8n_activate_workflow
Idempotent

Activate a workflow to enable automated execution based on its triggers. Use this tool to start automated processes in n8n.

Instructions

Activate a workflow so it can run automatically based on its triggers.

Args:

  • id (string): Workflow ID to activate

Returns: The activated workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique identifier of the resource

Implementation Reference

  • Handler function for the n8n_activate_workflow tool.
      async (params: z.infer<typeof IdParamSchema>) => {
        const workflow = await post<N8nWorkflow>(`/workflows/${params.id}/activate`);
        
        return {
          content: [{ type: 'text', text: `✅ Workflow activated!\n\n${formatWorkflow(workflow)}` }],
          structuredContent: workflow
        };
      }
    );
  • Tool registration for n8n_activate_workflow.
      server.registerTool(
        'n8n_activate_workflow',
        {
          title: 'Activate n8n Workflow',
          description: `Activate a workflow so it can run automatically based on its triggers.
    
    Args:
      - id (string): Workflow ID to activate
    
    Returns:
      The activated workflow.`,
          inputSchema: IdParamSchema,
          annotations: {
            readOnlyHint: false,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false
          }
        },
        async (params: z.infer<typeof IdParamSchema>) => {
          const workflow = await post<N8nWorkflow>(`/workflows/${params.id}/activate`);
          
          return {
            content: [{ type: 'text', text: `✅ Workflow activated!\n\n${formatWorkflow(workflow)}` }],
            structuredContent: workflow
          };
        }
      );
Behavior3/5

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

Annotations cover key traits (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description doesn't need to repeat these. It adds value by explaining the purpose ('run automatically based on its triggers'), but lacks details on side effects (e.g., enabling triggers), error conditions, or rate limits. No contradiction with annotations.

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 front-loaded with the core purpose in the first sentence, followed by structured Args and Returns sections. It's efficient with minimal waste, though the Args/Returns formatting could be more integrated into natural language for better flow.

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?

Given the tool's moderate complexity (activation operation), rich annotations, and no output schema, the description is adequate but incomplete. It explains what activation does but omits details like return format (beyond 'The activated workflow'), error handling, or dependencies on workflow state, leaving gaps for an agent to infer.

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%, with the parameter 'id' documented as 'The unique identifier of the resource'. The description adds no extra meaning beyond this, such as format examples or where to find the ID. Baseline 3 is appropriate since the schema already provides adequate parameter information.

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 clearly states the action ('Activate a workflow') and the outcome ('so it can run automatically based on its triggers'), which is specific and meaningful. However, it doesn't explicitly differentiate from its sibling 'n8n_deactivate_workflow' beyond the obvious opposite action, missing an opportunity to clarify the distinction in behavior or context.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'n8n_run_workflow' for manual execution or 'n8n_deactivate_workflow' for stopping automation. It lacks context on prerequisites (e.g., workflow must exist and be deactivated) or typical scenarios for activation.

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/DrBalls/n8n-mcp-server-v2'

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