Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

n8n: Deactivate workflow

n8n_deactivate_workflow
Destructive

Deactivate a workflow to stop automatic runs while keeping it available for manual execution.

Instructions

[UNIFIED] Deactivate a workflow. It will no longer run automatically but can still be executed manually.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "workflow_id": "<workflow_id>"
    },
    "name": "n8n_deactivate_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
workflow_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is to explain the actual consequence, which it does: automatic execution stops while manual execution remains possible. It omits error cases (unknown workflow_id, already-inactive workflow) and the fact that the tool is flagged non-idempotent, but the core state change is disclosed.

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

Conciseness5/5

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

Two short sentences with the action front-loaded and the consequence immediately after; nothing is redundant, and the total length is proportionate to a simple toggle tool.

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?

For a two-parameter toggle with no output schema and usable annotations, the definition covers the essential effect. It falls short on parameter meaning (0% coverage) and on failure/authorization behavior, which matter when the tool changes live automation state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there are two required parameters, yet the description says nothing about either. The meaning of "site" (which n8n instance/tenant) and the expected form of "workflow_id" are left entirely to the agent's inference, which is a real gap for a mutation tool.

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 names a specific verb and resource ("Deactivate a workflow") and states the concrete effect: it stops automatic runs. The clause "can still be executed manually" implicitly distinguishes it from n8n_delete_workflow, but no sibling is named outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the right tool when it wants to pause automation without deleting the workflow. There is no explicit when-to-use / when-not-to-use guidance and no pointer to n8n_activate_workflow as the inverse or n8n_delete_workflow as the destructive alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools