Skip to main content
Glama

create_folder

Create folders in Langflow to organize flows with optional nested hierarchy for project-based workflow management.

Instructions

Create a new folder for organizing flows with optional nested hierarchy.

Purpose: Establish organizational structure in Langflow by creating folders to group related flows. Supports hierarchical organization through nested folders, enabling project-based or team-based flow management. Essential for maintaining organized workspace with many flows.

Parameters:

  • name (required, string, max: 255 chars): Folder display name (should be descriptive and unique)

  • description (optional, string): Purpose and contents description for documentation

  • parent_id (optional, UUID string): Parent folder ID for creating nested subfolder hierarchy (use list_folders to find valid parent IDs)

Returns: FolderRead object containing:

  • id (UUID): Newly created folder's unique identifier (use this as folder_id when creating/organizing flows)

  • name (string): Folder display name

  • description (string): Folder description

  • parent_id (UUID): Parent folder ID if nested, null for root-level folder

  • created_at, updated_at (ISO timestamps): Folder lifecycle timestamps

Usage Examples:

  1. Create root folder: { name: "Production Flows" }

  2. Folder with description: { name: "Customer Services", description: "Customer-facing automation workflows" }

  3. Create nested subfolder: { name: "API Integrations", parent_id: "parent-folder-uuid" }

  4. Project organization: { name: "Q1 2024 Project", description: "First quarter automation initiatives" }

Best Practices:

  • Use descriptive, hierarchical names (e.g., "Marketing/Email Campaigns" structure via nesting)

  • Add descriptions to document folder purpose and ownership

  • Plan folder hierarchy before creation (root categories, then subcategories)

  • Create folders before flows to enable immediate organization

  • Use consistent naming conventions across team (e.g., "Team - Project - Category")

  • Limit nesting depth to 2-3 levels for maintainability

  • Cache created folder IDs for subsequent flow creation operations

Common Errors:

  • "Folder name already exists": Choose unique name or create in different parent folder

  • "Invalid parent folder ID": Ensure parent_id is valid UUID from list_folders

  • "Parent folder not found": parent_id doesn't exist or was deleted

  • "Name is required": Must provide name parameter

  • "Maximum nesting depth exceeded": Too many nested levels (flatten hierarchy)

  • "Circular reference detected": parent_id creates loop in folder structure

Related Tools:

  • list_folders: Browse existing folders before creating new ones

  • update_folder: Modify folder name, description, or move to different parent

  • create_flow: Create flows organized within this folder using returned ID

  • get_folder: Retrieve folder details after creation

  • delete_folder: Remove folder when no longer needed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFolder name (required)
parent_idNoOptional parent folder ID (UUID) for nested folders
descriptionNoOptional folder description
Behavior4/5

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

No annotations are provided, so the description carries full responsibility. It discloses the creation behavior, support for nesting, return of FolderRead object with timestamps, and lists common errors like 'Maximum nesting depth exceeded' and 'Circular reference detected'. It does not address authorization or rate limits, but these are not critical for a create operation.

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 well-structured with clear sections (Purpose, Parameters, Returns, Examples, Best Practices, Errors, Related Tools). It is somewhat lengthy but each section adds value. The front-loading of purpose and parameters is effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 3 parameters and no output schema, the description compensates thoroughly. It explains the return object in detail, covers common errors, best practices, and related tools. The agent has all necessary information to use the tool correctly.

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?

Schema coverage is 100% (all three parameters in schema and description). The description adds extra meaning: name has max 255 chars and uniqueness suggestion, parent_id references list_folders, description is for documentation. This exceeds the baseline of 3 by providing valuable context beyond schema.

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 explicitly states the tool's action: 'Create a new folder for organizing flows with optional nested hierarchy.' It clearly identifies the resource (folder), verb (create), and context (organizing flows, supporting hierarchy). This clearly distinguishes it from sibling tools like list_folders, update_folder, and delete_folder, which handle different operations.

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

Usage Guidelines5/5

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

The description includes a 'Related Tools' section that advises using list_folders to find parent IDs and update_folder to modify folders. Best practices guide the agent on planning hierarchy, caching IDs, and consistent naming. Common errors provide troubleshooting guidance. This gives explicit when and when-not guidance.

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/nobrainer-tech/langflow-mcp'

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