Skip to main content
Glama
nobrainer-tech

langflow-mcp-server

by nobrainer-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

run_flow_advanced

Execute Langflow flows with input arrays, parameter tweaks, session continuity, streaming, and user-scoped outputs.

Instructions

Advanced flow execution using Langflow 1.11.x input/output request arrays, tweaks, sessions, and streaming.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputsNoInputValueRequest array with optional components, input_value, session, and type
streamNoEnable streaming mode (default: false)
tweaksNoComponent-specific parameter overrides
outputsNoOptional output component names or IDs
user_idNoUser ID (UUID) for user-scoped execution
session_idNoSession ID for conversation continuity
flow_id_or_nameYesFlow ID (UUID) or flow name to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv4.12.2
    • removedInput schema / properties / input_type
      Removed value: -{
-  "description": "Type of input (e.g., \"chat\", \"text\")",
-  "type": "string"
-}
    • removedInput schema / properties / input_value
      Removed value: -{
-  "description": "Input value for the flow",
-  "type": "string"
-}
    • addedInput schema / properties / inputs
      Added value: +{
+  "description": "InputValueRequest array with optional components, input_value, session, and type",
+  "type": [
+    "array",
+    "null"
+  ]
+}
    • removedInput schema / properties / output_component
      Removed value: -{
-  "description": "Specific output component to retrieve results from",
-  "type": "string"
-}
    • removedInput schema / properties / output_type
      Removed value: -{
-  "description": "Expected output type (e.g., \"chat\", \"text\", \"json\")",
-  "type": "string"
-}
    • addedInput schema / properties / outputs
      Added value: +{
+  "description": "Optional output component names or IDs",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
    • changedInput schema / properties / session_id / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / tweaks / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
  2. First observedv4.11.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether execution is synchronous or long-running, what auth is required, whether tweaks persist, or how streaming changes the response — it only names features that already appear in the schema.

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?

A single front-loaded sentence with no filler. It is efficient, though the compactness comes at the cost of detail rather than being dense with useful information.

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

Completeness2/5

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

For a 7-parameter, no-annotation, no-output-schema execution tool, the description omits prerequisites, execution semantics, return behavior, and any positioning against its many execution siblings. It is not complete enough to confidently invoke.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all seven parameters. The description's mention of 'request arrays, tweaks, sessions, and streaming' loosely maps onto those params and adds version context (Langflow 1.11.x), but no syntax or constraint beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a recognizable verb+resource (flow execution) and enumerates the advanced feature set it supports (input/output request arrays, tweaks, sessions, streaming). However, it never distinguishes itself from the very similar siblings run_flow, run_flow_session, process_flow, or predict_flow, so an agent cannot tell from the text alone when 'advanced' execution is the right choice.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no named alternative. Given the crowded sibling set (run_flow, run_flow_session, process_flow, predict_flow, run_workflow), the agent is left to guess which execution tool to pick.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools