Skip to main content
Glama
nikolausm

n8n MCP Server

by nikolausm

deactivate_workflow

Stop a running workflow by providing its workflow ID. Disable active automation processes when needed.

Instructions

Deactivate a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesThe ID of the workflow to deactivate

Implementation Reference

  • src/tools.ts:147-160 (registration)
    Registration of the 'deactivate_workflow' tool with name, description, and inputSchema requiring workflowId.
    {
      name: "deactivate_workflow",
      description: "Deactivate a workflow",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "The ID of the workflow to deactivate",
          },
        },
        required: ["workflowId"],
      },
    },
  • Handler case that parses workflowId using WorkflowIdSchema and calls client.deactivateWorkflow().
    case "deactivate_workflow": {
      const { workflowId } = WorkflowIdSchema.parse(args);
      return await client.deactivateWorkflow(workflowId);
    }
  • Client method that sends a PATCH request to /api/v1/workflows/{id} with active: false to deactivate a workflow.
    async deactivateWorkflow(id: string) {
      const response = await this.client.patch(`/api/v1/workflows/${id}`, {
        active: false,
      });
      return WorkflowSchema.parse(response.data);
    }
  • Zod schema used for parsing the workflowId input argument for deactivate_workflow.
    const WorkflowIdSchema = z.object({
      workflowId: z.string(),
    });
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'deactivate' without explaining what that entails (e.g., irreversible? affects running executions?). It fails to describe side effects or permissions needed.

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 a single, front-loaded sentence that is extremely concise. However, it omits important context that could be added in a second sentence without sacrificing conciseness.

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 no output schema and no annotations, the description is incomplete. It does not explain the effect of deactivation, reversibility, or what happens to related executions. For a mutation tool, more context is needed.

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 coverage is 100%, so the description adds no additional meaning beyond the schema parameter description. Baseline 3 is appropriate as the schema already documents the parameter sufficiently.

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 'Deactivate a workflow' is a specific verb+resource combination that clearly communicates the action and target. It distinguishes itself from sibling tools like 'activate_workflow' and 'delete_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 on when to use this tool versus alternatives is provided. It does not mention the implications of deactivating a workflow (e.g., stopping triggers, impact on running executions) or any prerequisites.

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