Skip to main content
Glama

deployed

Lists all workflows in an n8n instance, replacing the "n8n list:workflow" command for workflow management and deployment.

Instructions

List all workflows in n8n instance - replaces "n8n list:workflow" command

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration and schema definition for the 'deployed' tool. Provides empty input schema (no parameters) and description.
      name: 'deployed',
      description: 'List all workflows in n8n instance - replaces "n8n list:workflow" command',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Tool handler dispatch case for 'deployed' tool within the central ToolHandler.handleTool() method. Delegates to N8nManager.listDeployedWorkflows().
    case 'deployed':
      return await this.n8nManager.listDeployedWorkflows();
  • Core handler implementation in N8nManager. Executes 'n8n list:workflow --all', parses id|name output, checks active status separately, filters warnings, and returns formatted markdown list of deployed workflows with status indicators.
    async listDeployedWorkflows(): Promise<any> {
      try {
        const command = 'n8n list:workflow --all';
        
        console.error(`Executing: ${command}`);
        const { stdout, stderr } = await execAsync(command);
        
        if (this.hasRealError(stderr, stdout)) {
          throw new Error(stderr);
        }
    
        // Parse the output - format is "id|name"
        const lines = stdout.split('\n').filter(line => line.trim() && !line.includes('deprecation'));
        const workflows = [];
        
        // Get active workflow IDs for status
        let activeIds: string[] = [];
        try {
          const activeCommand = 'n8n list:workflow --active=true --onlyId';
          const { stdout: activeStdout } = await execAsync(activeCommand);
          activeIds = activeStdout.split('\n').filter(id => id.trim()).map(id => id.trim());
        } catch {
          // If we can't get active status, continue without it
        }
        
        for (const line of lines) {
          // Skip warning lines
          if (line.includes('There are deprecations') || line.includes('DB_SQLITE') || line.includes('N8N_RUNNERS')) {
            continue;
          }
          
          // Parse n8n list output format: id|name
          const parts = line.split('|');
          if (parts.length >= 2) {
            const id = parts[0].trim();
            workflows.push({
              id: id,
              name: parts[1].trim(),
              status: activeIds.includes(id) ? 'active' : 'inactive',
            });
          }
        }
    
        let output = `📋 Deployed Workflows (${workflows.length}):\n\n`;
        
        if (workflows.length === 0) {
          output += 'No workflows found in n8n instance.\n';
        } else {
          for (const wf of workflows) {
            const statusIcon = wf.status === 'active' ? '🟢' : '⚪';
            output += `${statusIcon} [${wf.id}] ${wf.name}\n`;
          }
        }
    
        return {
          content: [
            {
              type: 'text',
              text: output,
            },
          ],
        };
      } catch (error: any) {
        throw new Error(`Failed to list workflows: ${error.message}`);
      }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool lists workflows but does not disclose behavioral traits such as whether it requires authentication, how results are formatted, if there are rate limits, or what happens with large result sets. The description is minimal and lacks essential operational context.

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 single, efficient sentence that front-loads the core purpose and includes only necessary additional context (the command replacement). There is zero waste, making it appropriately sized and well-structured.

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's simplicity (0 parameters, no output schema, no annotations), the description is adequate as a minimum viable explanation. However, it lacks details on output format or behavioral aspects, which could be helpful for an agent despite the low complexity. It meets basic needs but has clear gaps in completeness.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not add parameter details, maintaining focus on the tool's purpose without redundancy. Baseline is 4 for zero parameters.

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 specific action ('List all workflows') and resource ('in n8n instance'), with explicit differentiation from a sibling command ('replaces "n8n list:workflow" command'). It provides verb+resource+scope and distinguishes from alternatives.

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 implies usage context by mentioning it replaces a specific command, giving clear guidance on when to use this tool. However, it does not explicitly state when NOT to use it or name alternative tools among the siblings for different scenarios.

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/mckinleymedia/mcflow-mcp'

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