Skip to main content
Glama

list

View all n8n workflows in your project to manage automation processes. Filter by project name to organize workflows efficiently.

Instructions

List all n8n workflows in this project (use deployed to see workflows in n8n)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoOptional project name to filter workflows

Implementation Reference

  • Executes the 'list' tool by calling workflowManager.listWorkflows with optional project argument.
    case 'list':
      return await this.workflowManager.listWorkflows(args?.project as string);
  • Tool definition including name, description, and input schema for the 'list' tool.
      name: 'list',
      description: 'List all n8n workflows in this project (use deployed to see workflows in n8n)',
      inputSchema: {
        type: 'object',
        properties: {
          project: {
            type: 'string',
            description: 'Optional project name to filter workflows',
          },
        },
      },
    },
  • Registers the list of tools (including 'list') via MCP ListToolsRequestHandler.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: getToolDefinitions(),
    }));
  • Registers the generic tool call handler that dispatches to ToolHandler.handleTool based on tool name.
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      return await this.toolHandler.handleTool(
        request.params.name,
        request.params.arguments
      );
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool lists workflows in 'this project' and references 'deployed' for n8n workflows, but it doesn't disclose key behavioral traits such as whether it's read-only, if it requires authentication, what the output format is, or any rate limits. This is a significant gap for a tool with no annotation coverage.

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?

The description is a single, efficient sentence that front-loads the main purpose and includes a brief alternative reference. There's no wasted text, but it could be slightly more structured by separating the alternative into its own sentence for clarity.

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 low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and hints at an alternative, but it lacks details on behavior, output, or integration with siblings, making it incomplete for optimal agent use.

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?

The input schema has 100% description coverage, with one parameter ('project') documented as 'Optional project name to filter workflows'. The description doesn't add any meaning beyond this, such as explaining what constitutes a 'project' or how filtering works. Baseline score of 3 is appropriate since the schema does the heavy lifting.

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?

The description clearly states the verb ('List') and resource ('n8n workflows in this project'), making the purpose specific and understandable. It distinguishes from the sibling 'deployed' tool by noting that 'deployed' shows workflows in n8n, but it doesn't explicitly differentiate from other list-like siblings such as 'list_code' or 'list_credentials', which keeps it from a perfect score.

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

Usage Guidelines3/5

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

The description implies usage by suggesting 'deployed' as an alternative for viewing workflows in n8n, but it doesn't provide explicit guidance on when to use this tool versus other list-related siblings like 'list_code' or 'list_credentials'. No exclusions or prerequisites are mentioned, leaving some ambiguity.

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