MCP Make.com Server

get_scenario_blueprint

Retrieve the full blueprint of a Make.com scenario by ID to understand its flow and logic.

Instructions

Get the full blueprint (flow definition) of a scenario

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": "get_scenario_blueprint"
  }
}

Input Schema

Name	Required	Description	Default
`scenarioId`	Yes	Scenario ID

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?

No annotations are provided, so the description carries the full burden. 'Get' implies a read-only operation, but the description does not disclose any other behavioral traits such as authentication requirements, rate limits, error behavior, or what 'full blueprint' entails structurally.

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?

The description is a single, front-loaded sentence with no wasted words. It is appropriately sized for the tool's purpose.

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?

With no output schema and no annotations, the description should compensate by describing the return value or key behavioral aspects. It does not explain what a blueprint contains (e.g., nodes, edges, flow logic) or any other details an agent would need to use the tool confidently.

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 description coverage is 100%, so the single scenarioId parameter is fully documented in the schema. The description adds no additional meaning about the parameter, which is acceptable given the high coverage.

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 states a specific verb ('Get') and resource ('full blueprint (flow definition) of a scenario'), which distinguishes it from the sibling get_scenario by focusing on the flow definition. However, it does not explicitly contrast itself with get_scenario or other siblings, so it stops short of full sibling differentiation.

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?

There is no guidance on when to use this tool versus get_scenario, list_scenarios, or any other alternative. The description gives no context for selection or exclusions.

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