Skip to main content
Glama
nobrainer-tech

langflow-mcp-server

by nobrainer-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_shared_sessions

Fetch shared session IDs for a Langflow source flow, ordered by message timestamp descending, with an optional limit.

Instructions

List the newest shared session IDs for a source flow, ordered by latest message timestamp descending. Langflow returns 100 by default, at most 200; limit 0 uses the default. Older sessions beyond the cap are not returned.

Input Schema

NameRequiredDescriptionDefault
limitNoSession limit; omitted or 0 uses 100, upstream clamps values above 200
source_flow_idYesSource flow ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.12.3
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Session limit; omitted or 0 uses 100, upstream clamps values above 200",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv4.11.0

TDQS

A3.5/5.0
Behavior4/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 well on the important behavior: it discloses the default of 100, the 200 ceiling, that limit 0 falls back to the default, and that sessions beyond the cap are silently dropped. It does not state permissions or that the operation is read-only, but the truncation semantics are the material risk here and they are covered.

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?

Three tight sentences with no filler, front-loaded with what is returned and how it is ordered before the cap details. Minor redundancy with the limit parameter's schema description keeps it from being maximally efficient.

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

Completeness4/5

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

For a simple two-parameter read tool with no output schema, the description covers what is returned (session IDs), the sort order, and the pagination ceiling. It would be stronger if it noted auth or the ID format, but nothing needed to call it correctly is missing.

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 coverage is 100% and the limit parameter's schema already documents the default, the clamp at 200, and the limit-0 behavior, so the description largely restates structured data. The only added framing is the ordering rule, which is not parameter-specific, so this sits at the baseline.

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?

States a specific verb and resource (list newest shared session IDs) scoped to a source flow, and adds the ordering rule (latest message timestamp descending). It is clearly distinct from get_shared_messages by returning session IDs rather than messages, though it never names that sibling explicitly.

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, no prerequisites, and no routing between this and siblings such as get_shared_messages or get_monitor_sessions. The purpose is inferable, but nothing in the text tells the agent when this tool is the right choice.

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