Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

n8n: Get workflow

n8n_get_workflow
Read-only

Retrieve detailed information about a specific n8n workflow, including its nodes, connections, and settings, so you can inspect or troubleshoot automation logic by site and workflow ID.

Instructions

[UNIFIED] Get detailed information about a specific workflow 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": {
      "site": "<site>",
      "workflow_id": "<workflow_id>"
    },
    "name": "n8n_get_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

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description's added value is limited to naming the returned payload sections (nodes, connections, settings). It does not disclose auth requirements, rate limits, response size for large workflows, or what happens when the workflow_id does not exist.

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 well-formed sentence with the resource and returned fields front-loaded and no wasted clauses. The '[UNIFIED]' prefix is minor noise that adds no semantic value to the agent.

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 two-parameter read tool with annotations and no output schema, the definition is minimally adequate. It falls short on explaining the required 'site' parameter and on any behavioral caveats, which matters because nothing else in the definition covers them.

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%, so the description carries the full burden for the two parameters, and it only weakly implies workflow_id via 'specific workflow'. The 'site' parameter, which presumably selects an n8n instance, is left entirely unexplained in both schema and description.

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 (get) and resource (workflow) and enumerates what is returned: nodes, connections, and settings. That is clearly distinguishable from siblings like n8n_get_workflow_tags or n8n_update_workflow, though the description does not explicitly name those alternatives.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as n8n_get_workflow_tags for tag data or n8n_get_execution for run data. The agent must infer the appropriate context from the tool name and the word 'specific' alone.

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