Screenrove: UI Design Reference & Screenshots (free Mobbin alternative)

List captured onboarding flows

list_flows

Read-only

List captured user journeys (signup and onboarding, checkout, booking, search, marketplace, and task flows such as building a board) with step counts and flow type, 40 at a time. A flowType marked typeInferred was read from the flow's first steps; flows with no type are left out of a flowType filter and counted in untyped. get_flow gives the steps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_flows"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Flows per page, 1 to 100.
`offset`	No	Results to skip; pass nextOffset from the previous page.
`flowType`	No	Only return flows of this type. Untyped flows are counted, not shown.

Output Schema

Name	Required	Description	Default
`next`	No
`flows`	No
`limit`	No
`notes`	No
`total`	No
`offset`	No
`message`	No
`untyped`	No
`nextOffset`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 30, 2026

changedInput schema / properties / flowType / description

Previous value: -"Only return flows of this type."New value: +"Only return flows of this type. Untyped flows are counted, not shown."

addedInput schema / properties / limit

Added value: +{
+  "default": 40,
+  "description": "Flows per page, 1 to 100.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Results to skip; pass nextOffset from the previous page.",
+  "minimum": 0,
+  "type": "integer"
+}

removedOutput schema / properties / flows / items

Removed value: -{
-  "properties": {
-    "branchCount": {
-      "description": "Steps that are alternate branches (not the main path).",
-      "type": "integer"
-    },
-    "flowTitle": {
-      "description": "Human-readable title for the flow",
-      "type": "string"
-    },
-    "flowType": {
-      "description": "What the flow accomplishes.",
-      "enum": [
-        "signup-onboarding",
-        "search",
-        "checkout",
-        "booking",
-        "marketplace"
-      ],
-      "type": "string"
-    },
-    "handoffId": {
-      "description": "Use with buildHandoff",
-      "type": "string"
-    },
-    "productId": {
-      "type": "string"
-    },
-    "productName": {
-      "type": "string"
-    },
-    "scope": {
-      "description": "What was captured. marketing: logged-out marketing pages only. public-demo: logged out, but real\nproduct surfaces or public demos were used. task-incomplete: signed in, but the journey stops before\nits result. signed-in: signed in, and the journey reaches its result.\n",
-      "enum": [
-        "marketing",
-        "public-demo",
-        "task-incomplete",
-        "signed-in"
-      ],
-      "type": "string"
-    },
-    "stepCount": {
-      "description": "Total steps including branches.",
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}

addedOutput schema / properties / limit
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / next
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / nextOffset
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / notes
```
Added value: +{
+  "type": "array"
+}
```
addedOutput schema / properties / offset
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / untyped
```
Added value: +{
+  "type": "integer"
+}
```

Changed1 schema field changedOct 22, 2026

addedOutput schema / properties / flows / items / properties / scope

Added value: +{
+  "description": "What was captured. marketing: logged-out marketing pages only. public-demo: logged out, but real\nproduct surfaces or public demos were used. task-incomplete: signed in, but the journey stops before\nits result. signed-in: signed in, and the journey reaches its result.\n",
+  "enum": [
+    "marketing",
+    "public-demo",
+    "task-incomplete",
+    "signed-in"
+  ],
+  "type": "string"
+}

AddedSep 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/destructive=false. The description adds real behavioral context beyond them: typeInferred provenance, that untyped flows are excluded from a flowType filter but counted, and the page size. It does not mention ordering of results, but the added semantics are substantial.

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?

Front-loads the resource and return fields, then the pagination and typing caveats. Dense but every clause carries information; slightly long single sentence but not padded.

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?

With annotations, a full input schema, and an output schema present, the description covers what an agent needs: scope, page size, filter behavior, and where to get step detail. Ordering of results is the only minor omission.

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 coverage is 100% so the baseline is 3, but the description adds meaning not in the schema: how typeInferred values are derived and that untyped flows are counted rather than returned. This extends the flowType semantics usefully.

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?

States a specific verb+resource ('List captured user journeys') with the returned fields (step counts, flow type) and names the sibling get_flow for step detail. An agent can distinguish it from get_flow and search_screens without opening a schema.

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

Usage Guidelines4/5

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

Clear usage context: batch listing 40 at a time, with a pointer to get_flow when steps are needed. It doesn't explicitly state when to prefer this over other sibling listing tools (e.g., search_screens), so it stops short of full alternative routing.

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

All Screenrove: UI Design Reference & Screenshots (free Mobbin alternative) tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?