MCP Make.com Server

deactivate_scenario

Stops a Make.com scenario from running by deactivating it using the required scenario ID.

Instructions

Deactivate a scenario to stop it from running

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": {
      "scenarioId": "<scenarioId>"
    },
    "name": "deactivate_scenario"
  }
}

Input Schema

Name	Required	Description	Default
`scenarioId`	Yes	Scenario ID to deactivate

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a mutation. It does not state whether deactivation is reversible, what happens to in-flight runs, required permissions, or the resulting state beyond 'stops running'.

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?

A single short, front-loaded sentence with no filler. It is efficient, though the clause 'to stop it from running' is somewhat redundant with 'deactivate'.

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 simple one-parameter mutation the description is minimally adequate, but with no annotations and no output schema it should at least state reversibility and what deactivation does to an already-running scenario.

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 single parameter has 100% schema description coverage ('Scenario ID to deactivate'), so the schema already carries the semantics. The description adds nothing beyond it, making the baseline 3 appropriate.

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?

States a specific verb (deactivate) and resource (scenario), and the phrase 'to stop it from running' conveys the effect. It does not distinguish itself from siblings like delete_scenario or activate_scenario, which is the main gap.

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 versus delete_scenario (permanent removal) or activate_scenario (the inverse). The purpose is implied by the verb, but no conditions, prerequisites, or alternatives are named.

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