Skip to main content
Glama

N8n

by io.github.pipeworx-io
OverviewAdmin

N8n List Workflows

n8n_list_workflows
Read-onlyIdempotent

List workflows in YOUR n8n instance, with an active/inactive breakdown. Answers "how many active workflows do we have", "list our n8n workflows", "which workflows are turned on". Each workflow: id, name, active (on/off), createdAt, updatedAt, tags. Set active_only:true to list just the live ones. Requires your instance_url + n8n API key (_apiKey).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax workflows to fetch (1-250, default 100).
_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.
active_onlyNoOnly return active (turned-on) workflows. Default false (all).
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"
+  },
+  {
+    "_apiKey": "your-n8n-api-key",
+    "active_only": true,
+    "instance_url": "https://n8n.example.com",
+    "limit": 50
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate a safe read-only, idempotent operation. The description adds useful context by stating the required credentials (instance_url and API key) and the fields returned per workflow, which is valuable beyond the annotations. No contradiction with 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 a compact, front-loaded paragraph that conveys purpose, examples, return fields, and a filtering option in just a few sentences. Every sentence adds value without redundancy.

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

Completeness4/5

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

The description covers the essential behavioral aspects: what it lists, the breakdown, authentication requirements, and return fields. While there is no output schema, the description compensates by naming the fields. It is not overly complex, and the annotations provide safety context, so this is reasonably complete.

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% and each parameter already has a clear description. The tool description does not add meaning beyond what the schema provides; it only repeats the active_only behavior already documented. Baseline 3 is appropriate since the schema handles parameter semantics.

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 lists workflows in the user's n8n instance with an active/inactive breakdown, and provides example questions it answers. This distinguishes it from sibling tools like n8n_get_workflow and n8n_list_executions, making the purpose unambiguous.

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 gives clear context for when to use the tool (e.g., answering questions about active workflows) and mentions the active_only flag for filtering. However, it does not explicitly exclude alternatives or reference sibling tools, so it lacks explicit when-not-to-use guidance.

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