Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

Get Available Node Types

n8n_get_node_types
Read-onlyIdempotent

Retrieve all available node types with descriptions and categories to identify workflow components for automation design in n8n.

Instructions

Get a list of all available node types in the n8n instance.

Returns: List of node types with their descriptions and categories.

Useful for understanding what nodes are available when creating workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the n8n_get_node_types tool, which fetches available node types from the /node-types API endpoint and formats them by category for display.
    async () => {
      // This endpoint may vary depending on n8n version
      const nodes = await get<Array<{ name: string; displayName: string; description?: string; group?: string[] }>>('/node-types');
      
      // Group by category
      const grouped: Record<string, string[]> = {};
      nodes.forEach(node => {
        const category = node.group?.[0] || 'Other';
        if (!grouped[category]) grouped[category] = [];
        grouped[category].push(`${node.displayName} (${node.name})`);
      });
      
      const text = Object.entries(grouped)
        .map(([category, nodeList]) => `**${category}**\n${nodeList.slice(0, 10).join('\n')}${nodeList.length > 10 ? `\n... and ${nodeList.length - 10} more` : ''}`)
        .join('\n\n');
      
      return {
        content: [{ type: 'text', text: `**Available Node Types (${nodes.length} total)**\n\n${text}` }],
        structuredContent: { count: nodes.length, nodes }
      };
    }
  • Registration of the n8n_get_node_types tool within the server.registerTool call.
      server.registerTool(
        'n8n_get_node_types',
        {
          title: 'Get Available Node Types',
          description: `Get a list of all available node types in the n8n instance.
    
    Returns:
      List of node types with their descriptions and categories.
    
    Useful for understanding what nodes are available when creating workflows.`,
          inputSchema: EmptySchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false
          }
        },
Behavior3/5

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

Annotations already provide key behavioral hints (readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false), covering safety and idempotency. The description adds value by specifying the return format ('List of node types with their descriptions and categories') and the scope ('all available node types'), which aren't covered by annotations. However, it doesn't disclose additional traits like rate limits, authentication needs, or performance characteristics.

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 front-loaded with the core purpose in the first sentence, followed by return details and usage context in two additional sentences. Every sentence adds value without redundancy, making it efficient and well-structured for quick understanding by an AI agent.

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?

Given the tool's simplicity (0 parameters, no output schema) and rich annotations, the description is complete enough for an agent to use it correctly. It explains what the tool does, what it returns, and when to use it. The lack of an output schema is mitigated by the description detailing the return format, though more specifics on structure could enhance 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 tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose and output. This meets the baseline for tools with no parameters, as it avoids unnecessary detail.

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 tool's purpose as 'Get a list of all available node types in the n8n instance,' which is a specific verb+resource combination. It distinguishes itself from sibling tools by focusing on node types rather than workflows, credentials, or other resources. However, it doesn't explicitly differentiate from potential similar tools like 'get_credential_schema' or 'get_workflow,' though those are clearly different 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 clear context for usage with 'Useful for understanding what nodes are available when creating workflows,' which implicitly suggests using this tool during workflow design. It doesn't explicitly state when not to use it or name alternatives, but the context is sufficient for an agent to infer its role among siblings like 'n8n_create_workflow' or 'n8n_list_workflows.'

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

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