Skip to main content
Glama

list-projects

Retrieve all projects from n8n workflow automation platform. Requires Enterprise license with project management features enabled.

Instructions

List all projects from n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientIdYes

Implementation Reference

  • The main handler function for the 'list-projects' tool within the CallToolRequestSchema handler. It retrieves the N8nClient instance and calls listProjects() on it.
    case "list-projects": {
      const { clientId } = args as { clientId: string };
      const client = clients.get(clientId);
      if (!client) {
        return {
          content: [{
            type: "text",
            text: "Client not initialized. Please run init-n8n first.",
          }],
          isError: true
        };
      }
    
      try {
        const projects = await client.listProjects();
        return {
          content: [{
            type: "text",
            text: JSON.stringify(projects.data, null, 2),
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: error instanceof Error ? error.message : "Unknown error occurred",
          }],
          isError: true
        };
      }
    }
  • Supporting method in N8nClient class that performs the API call to list projects.
    async listProjects(): Promise<N8nProjectList> {
      return this.makeRequest<N8nProjectList>('/projects');
    }
  • src/index.ts:508-517 (registration)
    Tool registration in the listTools response, including name, description, and input schema.
      name: "list-projects",
      description: "List all projects from n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.",
      inputSchema: {
        type: "object",
        properties: {
          clientId: { type: "string" }
        },
        required: ["clientId"]
      }
    },
  • TypeScript interface defining the structure of the projects list response from the n8n API.
    interface N8nProjectList {
      data: N8nProject[];
      nextCursor?: string;
    }
  • Input schema validation for the list-projects tool.
    inputSchema: {
      type: "object",
      properties: {
        clientId: { type: "string" }
      },
      required: ["clientId"]
    }
Behavior3/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 adds important context about license requirements and input format constraints ('Arguments must be provided as compact, single-line JSON'), which goes beyond basic functionality. However, it doesn't describe what the tool returns, pagination behavior, error conditions, or other operational characteristics that would be helpful for an agent.

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 extremely concise with only two sentences, both of which provide essential information. The first sentence states the core purpose, and the second provides critical prerequisites and formatting requirements. Every word earns its place with no wasted text.

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 moderate complexity (list operation with license requirements), no annotations, no output schema, and poor parameter documentation, the description does an adequate but incomplete job. It covers the license prerequisite well but leaves the parameter meaning, return format, and operational behavior unspecified, which creates gaps for an agent trying to use this tool effectively.

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

Parameters2/5

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

With 0% schema description coverage and one required parameter (clientId), the description provides no information about what clientId represents, its format, or its purpose. The schema only indicates it's a required string, so the description fails to compensate for the complete lack of parameter documentation in the schema.

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 ('all projects from n8n'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other list operations like list-executions or list-workflows, which would require mentioning what makes projects distinct from those other resources.

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 explicit prerequisites ('Requires n8n Enterprise license with project management features enabled'), which is excellent guidance on when this tool can be used. It doesn't mention when to use alternatives or compare it to other list operations, but the license requirement provides clear context for usage.

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/illuminaresolutions/n8n-mcp-server'

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