Skip to main content
Glama
nikolausm

n8n MCP Server

by nikolausm

activate_workflow

Activate a workflow to start its execution using its unique ID.

Instructions

Activate a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesThe ID of the workflow to activate

Implementation Reference

  • src/tools.ts:133-146 (registration)
    Tool definition/registration for 'activate_workflow' with input schema requiring workflowId.
    {
      name: "activate_workflow",
      description: "Activate a workflow",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "The ID of the workflow to activate",
          },
        },
        required: ["workflowId"],
      },
    },
  • Handler case for 'activate_workflow': validates args with WorkflowIdSchema, then calls client.activateWorkflow(workflowId).
    case "activate_workflow": {
      const { workflowId } = WorkflowIdSchema.parse(args);
      return await client.activateWorkflow(workflowId);
    }
  • The activateWorkflow method on N8nClient: sends a PATCH request to /api/v1/workflows/{id} with active: true and returns parsed WorkflowSchema.
    async activateWorkflow(id: string) {
      const response = await this.client.patch(`/api/v1/workflows/${id}`, {
        active: true,
      });
      return WorkflowSchema.parse(response.data);
    }
  • WorkflowIdSchema used by the handler — a Zod schema requiring a string 'workflowId'.
    const WorkflowIdSchema = z.object({
      workflowId: z.string(),
    });
  • src/index.ts:31-33 (registration)
    Server setup: tools array (including activate_workflow) is registered via ListToolsRequestSchema handler.
    // Register tool list handler
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
Behavior2/5

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

The description only says 'Activate a workflow' without any details on what activation entails (e.g., changing state, side effects, permissions). No annotations are provided to fill this gap.

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

Conciseness3/5

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

The description is extremely concise (one sentence) but lacks structure or front-loading of key information. It is not verbose, but it is under-specified.

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?

Given the simplicity of the tool (one parameter, no output schema), the description should at least explain what 'activate' means in terms of workflow state. It is incomplete.

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?

The input schema covers the parameter well (100% description coverage), so the description does not need to add much. The baseline is 3, and the description provides no extra meaning beyond the schema.

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

Purpose3/5

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

The description 'Activate a workflow' clearly states the verb and resource, but it is essentially a restatement of the tool name and does not distinguish from sibling tools like deactivate_workflow or execute_workflow.

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 provided on when to use this tool versus alternatives, nor are there any prerequisites or context about workflow states.

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

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