Skip to main content
Glama
nobrainer-tech

langflow-mcp-server

by nobrainer-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

run_public_workflow

Execute a public Langflow workflow by flow ID, streaming results without authentication.

Instructions

Run a public (unauthenticated-eligible) workflow (Langflow 1.11.x). Stream-only execution; streaming is not incrementally surfaced.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoAlways stream for public execution
filesNoFlow-scoped pre-uploaded file paths
flow_idYesFlow ID
session_idNoOptional caller session (max 256 characters)
input_valueNoChat-style input value (max 65536 characters)
stream_protocolNoStreaming protocol, for example langflow or agui
stop_component_idNoOptional partial-run stop component
start_component_idNoOptional partial-run start component

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv4.12.2
    • addedInput schema / properties / files
      Added value: +{
+  "description": "Flow-scoped pre-uploaded file paths",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
    • removedInput schema / properties / globals
      Removed value: -{
-  "description": "Request-level global variables",
-  "type": "object"
-}
    • addedInput schema / properties / input_value
      Added value: +{
+  "description": "Chat-style input value (max 65536 characters)",
+  "type": "string"
+}
    • removedInput schema / properties / inputs
      Removed value: -{
-  "description": "Workflow inputs",
-  "type": "object"
-}
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "Always stream for public execution",
+  "enum": [
+    "stream"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Optional caller session (max 256 characters)",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / start_component_id
      Added value: +{
+  "description": "Optional partial-run start component",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / stop_component_id
      Added value: +{
+  "description": "Optional partial-run stop component",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • removedInput schema / properties / stream
      Removed value: -{
-  "description": "Stream the run",
-  "type": "boolean"
-}
    • addedInput schema / properties / stream_protocol
      Added value: +{
+  "description": "Streaming protocol, for example langflow or agui",
+  "type": "string"
+}
  2. First observedv4.11.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two important traits: the workflow is unauthenticated-eligible and execution is stream-only with no incremental surfacing. Still missing are side-effect profile, return behavior, timeout, or idempotency, which are critical for an execution tool.

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?

Two tightly constructed sentences with zero filler, front-loading the core action and immediately adding the key behavioral constraints. Every clause earns its place.

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 an 8-parameter execution tool with no output schema and no annotations, the description is too thin. It doesn't explain what the tool returns, how to retrieve results (especially given no incremental streaming), or any auth/permission nuances beyond 'unauthenticated-eligible'.

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 defines all 8 parameters. The description adds no parameter-level semantics beyond what is in the schema (e.g., it does not clarify flow_id format, input_value usage, or the effect of stop/start component IDs). Baseline 3 is appropriate.

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 states a specific verb ('Run') and resource ('public workflow'), and qualifies it with 'unauthenticated-eligible' and 'Langflow 1.11.x'. This distinguishes it from generic siblings like run_flow or run_workflow, but it does not explicitly name an alternative or contrast its scope.

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

Usage Guidelines3/5

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

Usage is implied by 'public (unauthenticated-eligible)' and 'stream-only execution' – an agent can infer this is for public workflows requiring streaming. However, there is no explicit when-to-use vs. when-not guidance, nor any named alternative among the many run_* siblings.

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