Skip to main content
Glama

n8n_deactivate_workflow

Deactivate a specific workflow in n8n by providing its ID to pause automation processes.

Instructions

Deactivate a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWorkflow ID to deactivate

Implementation Reference

  • The handler implementation for n8n_deactivate_workflow, which calls n8nClient.deactivateWorkflow.
    case 'n8n_deactivate_workflow': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.deactivateWorkflow(args.id as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • src/index.ts:520-529 (registration)
    The registration of n8n_deactivate_workflow in the MCP tool list.
      name: 'n8n_deactivate_workflow',
      description: 'Deactivate a workflow',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Workflow ID to deactivate' },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers almost nothing. It does not explain what deactivation means (prevents triggers? pauses queue? preserves data?), whether the operation is reversible, or what success/failure looks like for a mutation operation.

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?

At three words, the description is brief, but this borders on under-specification rather than purposeful conciseness. No structural issues, but every sentence (singular) fails to earn its place by providing insufficient information for tool selection.

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?

For a mutation tool with no output schema and no annotations, the description is inadequate. It omits critical context: reversibility, impact on active executions, return value format, and differentiation from n8n_delete_workflow. Agents need this context to use the tool safely.

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 has 100% description coverage for its single parameter 'id'. The description adds no semantic value beyond the schema's 'Workflow ID to deactivate' text. With complete schema coverage, the baseline score applies.

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 'Deactivate a workflow' is a near-tautology that restates the tool name with minimal elaboration. While it identifies the resource (workflow) and action (deactivate), it fails to distinguish from siblings like n8n_activate_workflow or clarify scope (does it stop running executions or just prevent new ones?).

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 usage guidance provided. The description does not indicate when to use this versus n8n_activate_workflow (the inverse operation), nor does it mention prerequisites (e.g., workflow must be active) or side effects that would guide an agent's selection logic.

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