Skip to main content
Glama

get_flow

Retrieve complete details and configuration of a specific flow, including node graph, component configurations, and metadata, for inspection or debugging.

Instructions

Retrieve complete details and configuration of a specific flow.

Purpose: Fetch comprehensive information about a flow including its full node graph, component configurations, connections, and metadata. Essential for inspecting flow structure, debugging workflows, and preparing flows for modification or execution.

Parameters:

  • flow_id (required, UUID string): The unique identifier of the flow to retrieve (obtained from list_flows or create_flow)

Returns: FlowRead object containing:

  • id (UUID): Flow's unique identifier

  • name (string): Flow display name

  • description (string): Flow purpose description

  • folder_id (UUID): Parent folder identifier if organized

  • user_id (UUID): Owner user identifier

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

  • data (object): Complete flow structure including:

    • nodes (array): All component nodes with their configurations

    • edges (array): Connections between nodes

    • viewport (object): Canvas positioning data

    • description (string): Flow-level documentation

Usage Examples:

  1. Get flow details: { flow_id: "550e8400-e29b-41d4-a716-446655440000" }

  2. Inspect before modification: { flow_id: "flow-uuid-from-list" }

  3. Debug flow structure: { flow_id: "failing-flow-uuid" }

Best Practices:

  • Use list_flows first to discover available flow_id values

  • Cache flow data locally to reduce API calls when repeatedly accessing same flow

  • Check updated_at timestamp to detect if flow changed since last retrieval

  • Inspect data.nodes to understand flow's component structure

  • Review data.edges to trace data flow between components

  • Validate flow_id format (must be valid UUID) before making request

Common Errors:

  • "Flow not found": flow_id doesn't exist or was deleted (verify with list_flows)

  • "Invalid UUID format": flow_id must be valid UUID string (e.g., "550e8400-e29b-41d4-a716-446655440000")

  • "Unauthorized": API key lacks permission to access this flow

  • "Flow ID is required": Must provide flow_id parameter

  • Connection timeout: Check Langflow instance availability and network connectivity

Related Tools:

  • list_flows: Find available flow_id values

  • update_flow: Modify flow configuration after retrieval

  • run_flow: Execute flow after inspecting its structure

  • build_flow: Compile and validate flow structure

  • delete_flow: Remove flow after inspection confirms it's no longer needed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flow_idYesThe ID of the flow to retrieve
Behavior4/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It details the return structure (FlowRead object with nodes, edges, viewport) and common errors, implying it's a read-only operation. It does not contradict any annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear headings but is quite long for a simple retrieval tool. It could be more concise while retaining key information.

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, the description thoroughly explains the return object structure, common errors, and provides examples. It covers all necessary context for an agent 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 description coverage is 100% (one parameter flow_id with type string). The description adds that flow_id is a UUID, where to obtain it (list_flows, create_flow), and includes usage examples and validation advice, adding value beyond the 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 clearly states the tool retrieves complete details and configuration of a specific flow, using specific verbs like 'Retrieve' and 'Fetch'. It distinguishes between retrieving, modifying, and executing flows in the 'Related Tools' section.

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 provides explicit guidance on when to use this tool (inspect flow structure, debug, prepare for modification). It includes best practices (list_flows first, cache data, check timestamps) and explicitly lists alternative tools with explanations.

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