Skip to main content
Glama

N8n

by io.github.pipeworx-io
OverviewAdmin

N8n Get Workflow

n8n_get_workflow
Read-onlyIdempotent

Get one workflow's detail by id from your n8n instance — name, active state, node list (which integrations it uses), tags, timestamps. Get the id from n8n_list_workflows. Requires your instance_url + n8n API key (_apiKey).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesREQUIRED — your n8n API key (Settings → n8n API → Create an API key). Sent as the X-N8N-API-KEY header. No shared key exists for this pack.
workflow_idYesThe workflow id — from n8n_list_workflows.
instance_urlYesREQUIRED — your n8n instance base URL, e.g. "https://you.app.n8n.cloud" (n8n Cloud) or "https://n8n.example.com" (self-hosted). Must be a public https URL.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-n8n-api-key",
+    "instance_url": "https://n8n.example.com",
+    "workflow_id": "123"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing the tool as a safe read operation. The description adds valuable context beyond annotations: it lists the returned fields, explicitly mentions the auth requirement (instance_url + API key), and notes the id source. This goes beyond the baseline provided by annotations.

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 two sentences, front-loaded with the main purpose, and includes essential details (return fields, id source, auth requirement) without any fluff. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with 3 fully documented parameters, rich annotations, no output schema, and a clear prerequisite from a sibling tool, the description is complete. It explains what is returned, how to get the id, and what auth is needed. There are no significant gaps.

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

Parameters4/5

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

Schema coverage is 100% with detailed parameter descriptions (e.g., '_apiKey' is sent as X-N8N-API-KEY, instance_url format). The description adds extra meaning by stating that workflow_id comes from n8n_list_workflows, which is not in the schema, thereby clarifying the parameter's provenance and usage.

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 tool's purpose with a specific verb ('Get') and resource ('one workflow's detail by id'). It enumerates the returned fields (name, active state, node list, tags, timestamps), distinguishing it from list tools by emphasizing the 'by id' scope and explicitly referencing n8n_list_workflows as the source of the id.

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

Usage Guidelines4/5

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

The description provides clear usage context: 'Get the id from n8n_list_workflows' establishes a prerequisite workflow. It implies this tool is for fetching full details after listing workflows. However, it does not explicitly state when NOT to use it or mention alternatives (e.g., n8n_list_executions), so it lacks explicit exclusions.

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

All N8n toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources