Skip to main content
Glama

n8n_activate_workflow

Activate a specific workflow in n8n by providing its ID to enable automated processes and trigger scheduled tasks.

Instructions

Activate a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWorkflow ID to activate

Implementation Reference

  • Handler logic for the 'n8n_activate_workflow' tool in the MCP server request handler.
    case 'n8n_activate_workflow': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.activateWorkflow(args.id as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • src/index.ts:509-518 (registration)
    Registration of the 'n8n_activate_workflow' tool in the ListTools response.
      name: 'n8n_activate_workflow',
      description: 'Activate a workflow',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Workflow ID to activate' },
        },
        required: ['id'],
      },
    },
  • API client method to perform the HTTP POST request to activate a workflow.
    async activateWorkflow(id: string): Promise<any> {
      const response = await this.client.post(`/workflows/${id}/activate`);
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure burden. It fails to explain what activation entails (enabling execution triggers?), whether the operation is idempotent, what permissions are required, or side effects. Only the basic action is implied by the verb 'Activate'.

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?

Extremely brief at three words with no redundant phrases. However, the brevity borders on under-specification. The structure is efficient but lacks front-loaded value beyond the tool name itself.

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?

Despite being a single-parameter tool with complete schema coverage, the description is inadequate. It omits critical context: the prerequisite that a workflow must exist (created via n8n_create_workflow), what 'active' state means functionally, and how this relates to the sibling deactivate tool.

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 has 100% description coverage ('Workflow ID to activate'), so the baseline is 3. The description adds no additional semantic information about parameters, acceptable formats, or where to obtain the ID, but the schema carries this adequately.

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

Purpose2/5

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

The description 'Activate a workflow' is a tautology that restates the tool name (n8n_activate_workflow → 'Activate a workflow'). While the verb and resource are clear, it fails to distinguish from sibling tools like n8n_deactivate_workflow or explain what activation means in the n8n 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?

Description provides no guidance on when to use this tool versus alternatives. Specifically, it does not clarify the relationship with n8n_deactivate_workflow (the inverse operation) or when activation is appropriate versus other workflow operations.

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

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