n8n-free-mcp

Get workflow

get_workflow

Retrieve a complete workflow, including all nodes, connections, and settings, by providing its ID.

Instructions

Get a full workflow by ID, including nodes, connections and settings.

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": {
      "id": "<id>"
    },
    "name": "get_workflow"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Workflow ID
`excludePinnedData`	No	Exclude pinData (default true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description must cover behavioral traits. It adds context by listing what the full workflow includes, but it does not disclose side effects, permission requirements, rate limits, or response structure. For a read operation, safety is implied but not stated.

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 sentence that efficiently communicates the core purpose and included elements. It is appropriately front-loaded. However, it could add minimal additional context (e.g., mention the default of excludePinnedData) without becoming verbose.

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?

Given the tool has two parameters and no output schema, the description could elaborate on the return format or note the default value of excludePinnedData. It is adequate for a simple retrieval tool but lacks completeness in explaining expected output.

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%, with both parameters having descriptions. The tool description does not add extra meaning beyond what the schema provides (id as workflow ID, excludePinnedData as boolean excluding pinData). Per guidelines, baseline is 3 when coverage is high.

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 clearly states the verb 'Get' and the resource 'full workflow by ID', specifying the included elements (nodes, connections, settings). This distinguishes it from sibling tools like list_workflows (which likely returns summaries) and get_execution (a different resource).

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?

The description implies using this tool to retrieve a detailed workflow, but it does not explicitly state when to use it over alternatives like list_workflows or provide any exclusions. The usage context is implied but not clearly delineated.

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

Deploy Server