Skip to main content
Glama

list_flows

Retrieve and browse Langflow flows with pagination and folder filtering to discover workflows and manage collections.

Instructions

List Langflow flows with flexible filtering and pagination.

Purpose: Retrieve flows from your Langflow instance with optional pagination and organization filters. Essential for discovering available workflows, managing large flow collections, and browsing flows within specific folders.

Parameters:

  • page (optional, number, default: 1, min: 1): Page number for pagination

  • size (optional, number, default: 50, max: 100): Number of flows per page

  • folder_id (optional, UUID string): Filter flows within a specific folder

  • components_only (optional, boolean, default: false): Return only component flows (reusable flow components)

  • get_all (optional, boolean, default: true): Retrieve all flows ignoring pagination (use with caution for large datasets)

Returns: Array of FlowRead objects containing:

  • id (UUID): Unique flow identifier

  • name (string): Flow display name

  • description (string): Flow purpose description

  • folder_id (UUID): Parent folder if organized

  • user_id (UUID): Owner user identifier

  • created_at, updated_at (ISO timestamps): Flow lifecycle dates

  • data (object): Flow configuration with nodes, edges, and component definitions

Usage Examples:

  1. List recent flows (default): {}

  2. Paginate through flows: { page: 2, size: 20 }

  3. Flows in specific folder: { folder_id: "uuid-here" }

  4. Get all component flows: { components_only: true, get_all: true }

Best Practices:

  • Use pagination (page/size) for better performance instead of get_all

  • Filter by folder_id when working within organized projects

  • Keep page size <= 50 for optimal response times

  • Cache folder_id values to reduce API calls

  • Use get_all sparingly, only when you need complete dataset

Common Errors:

  • "Page size cannot exceed 100": Reduce size parameter to 100 or less

  • "Invalid folder ID format": Ensure folder_id is a valid UUID (use list_folders to get valid IDs)

  • Empty results: Check if folder_id exists or try removing filters

  • Connection timeout: Reduce page size or enable pagination instead of get_all

Related Tools:

  • create_flow: Create new flows after listing existing ones

  • get_flow: Retrieve complete flow details by ID from this list

  • list_folders: Find valid folder_id values for filtering

  • update_flow: Modify flows found in this list

  • delete_flow: Remove flows identified in this list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 1)
sizeNoNumber of items per page (default: 50, max: 100)
get_allNoGet all flows without pagination (default: true)
folder_idNoFilter by folder ID
components_onlyNoReturn only components (default: false)
Behavior5/5

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

No annotations provided, so description carries full burden. It details pagination behavior, filtering, return structure (FlowRead objects), and warns about get_all usage. Also lists common errors, adding transparency.

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?

Well-structured with clear sections (Purpose, Parameters, Returns, Usage Examples, Best Practices, Common Errors, Related Tools). Front-loaded with purpose. Every sentence adds value without redundancy.

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?

Despite no output schema, description includes detailed 'Returns' section explaining each field. Five parameters are fully explained with usage context. Overall, it is comprehensive for the tool's complexity.

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

Parameters5/5

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

Schema coverage is 100%, and description adds extensive meaning beyond schema: usage examples, best practices for each parameter (e.g., 'use pagination for better performance'), and common errors provide richer semantics.

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 'List Langflow flows with flexible filtering and pagination' and elaborates on the purpose. It distinguishes from sibling tools like get_flow (retrieves a single flow) and list_folders (for folders).

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?

Includes 'Best Practices' section with guidance on pagination vs get_all, filtering by folder. Also lists related tools implying alternatives. Lacks explicit 'when not to use' but provides enough context.

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