Skip to main content
Glama
nobrainer-tech

langflow-mcp-server

by nobrainer-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_monitor_sessions

Retrieve the newest Langflow chat session IDs, optionally filtered by flow ID, to inspect recent conversations.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
limitNoSession limit; omitted or 0 uses 100, upstream clamps values above 200
flow_idNoOptional flow ID (UUID) to filter sessions by flow

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

A4/5.0
Behavior4/5

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

No annotations, so the description carries full burden. It discloses the default 100 / max 200 cap, limit 0 fallback, ordering by latest message desc, and that older sessions are truncated — strong operational context for a read 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?

Four short sentences, front-loaded with the core action, each adding distinct information with no filler.

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?

Covers purpose, cap, ordering, and truncation. Missing only sibling routing guidance and whether the ID list includes metadata; adequate for a simple read-list tool without an output schema.

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 already documents limit clamping and flow_id UUID format. The description reinforces the cap and 0-default but adds little 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?

Explicitly states it lists chat session IDs, optionally filtered by flow, and distinguishes itself from siblings like get_session by describing the ordering and cap behavior.

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?

Mentions the optional flow filter, but doesn't state when to use this vs. get_monitor_messages, get_monitor_session_messages, or get_shared_sessions. No exclusions or alternatives are named.

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