Skip to main content
Glama

n8n_list_workflows

Retrieve and view all workflows from your n8n instance to manage automation processes and monitor workflow inventory.

Instructions

List all workflows in n8n

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of workflows to return (default: 50)
cursorNoCursor for pagination

Implementation Reference

  • The actual implementation of listing n8n workflows using the Axios client.
    async listWorkflows(params?: { limit?: number; cursor?: string }): Promise<any> {
      const queryParams = new URLSearchParams();
      if (params?.limit) queryParams.append('limit', params.limit.toString());
      if (params?.cursor) queryParams.append('cursor', params.cursor);
      const response = await this.client.get(`/workflows?${queryParams}`);
      return response.data;
    }
  • src/index.ts:445-455 (registration)
    Tool registration for n8n_list_workflows in the MCP server.
    {
      name: 'n8n_list_workflows',
      description: 'List all workflows in n8n',
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number', description: 'Number of workflows to return (default: 50)' },
          cursor: { type: 'string', description: 'Cursor for pagination' },
        },
      },
    },
  • The MCP request handler that delegates the n8n_list_workflows call to the n8nClient.
    case 'n8n_list_workflows': {
      const result = await n8nClient.listWorkflows({
        limit: (args?.limit as number) || 50,
        cursor: (args?.cursor as string) as string | undefined,
      });
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but fails to mention read-only nature, pagination behavior, whether results are sorted, or what data fields are returned (full objects vs. summaries).

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?

Extremely brief at 5 words, but not wasteful. However, given the lack of annotations and pagination complexity, the description is under-loaded rather than appropriately concise.

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?

Missing output description (no output schema present), pagination behavior explanation, and differentiation from similar tools. For a potentially high-volume list operation, the lack of completeness regarding result sets is a significant gap.

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 has 100% description coverage for both parameters (limit and cursor), establishing baseline 3. The description adds no additional parameter context (e.g., recommended limit values, cursor format), but none is strictly required given complete schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the basic action (List) and resource (workflows) but uses the word 'all' which contradicts the pagination parameters (limit/cursor) present in the schema. It fails to distinguish from sibling tool n8n_get_workflow (singular retrieval vs. list).

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?

No guidance provided on when to use this versus n8n_get_workflow or other retrieval siblings. No mention of pagination strategy or when to use cursor vs. initial fetch.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Shravan1610/n8n-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server