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

Get a product's onboarding flow

get_flow

Read-only

Get a product's captured flow: every step in order with title, notes, page url, observed transitions (button labels and where they lead) and which steps are alternate branches, plus the handoffId for build_handoff. Use it to study how a product structures signup, onboarding or a task; then get_screen_image on the steps you will copy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productId": "<productId>"
    },
    "name": "get_flow"
  }
}

Input Schema

Name	Required	Description	Default
`productId`	Yes	Product id from list_products, e.g. linear, stripe or airbnb.

Output Schema

Name	Required	Description	Default
`next`	No
`scope`	No
`steps`	No
`captured`	No
`flowType`	No
`flowTitle`	No
`handoffId`	No
`productId`	No
`productName`	No
`typeInferred`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 30, 2026

changedInput schema / properties / productId / description

Previous value: -"Product id from listProducts, e.g. linear, stripe or airbnb."New value: +"Product id from list_products, e.g. linear, stripe or airbnb."

removedOutput schema / properties / captured / format
```
Removed value: -"date"
```

removedOutput schema / properties / flowType / enum

Removed value: -[
-  "signup-onboarding",
-  "search",
-  "checkout",
-  "booking",
-  "marketplace"
-]

changedOutput schema / properties / flowType / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

removedOutput schema / properties / handoffId / description

Removed value: -"Use with buildHandoff to get the full prompt."

addedOutput schema / properties / next
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / scope / description

Removed value: -"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"

removedOutput schema / properties / scope / enum

Removed value: -[
-  "marketing",
-  "public-demo",
-  "task-incomplete",
-  "signed-in"
-]

removedOutput schema / properties / steps / items

Removed value: -{
-  "properties": {
-    "branch": {
-      "description": "True if this step is an alternate path",
-      "type": "boolean"
-    },
-    "id": {
-      "description": "The screenshot's id. A step that shows a product or marketing screen uses that screen's id.",
-      "type": "string"
-    },
-    "imageUrl": {
-      "type": "string"
-    },
-    "notes": {
-      "type": "string"
-    },
-    "previewUrl": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    },
-    "transitions": {
-      "items": {
-        "properties": {
-          "action": {
-            "description": "The button or link text.",
-            "type": "string"
-          },
-          "to": {
-            "description": "Where this action leads.",
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}

addedOutput schema / properties / typeInferred
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedOct 22, 2026

addedOutput schema / 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"
+}

addedOutput schema / properties / steps / items / properties / id / description

Added value: +"The screenshot's id. A step that shows a product or marketing screen uses that screen's id."

AddedSep 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds valuable substance by disclosing the shape of the payload (ordered steps, transition labels and destinations, branch flags) and the handoffId linkage to build_handoff. It does not discuss behavior for an unknown productId, but that is a minor gap against the existing output 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?

Two sentences, front-loaded with the returned content before the usage instruction. The return-value enumeration is long but each item is substantive; nothing is redundant filler.

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

Completeness5/5

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

For a single-parameter, read-only tool with an output schema, the description covers what it returns, when to reach for it, and the natural next tool. Nothing an agent needs in order to invoke 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?

Only one parameter and schema coverage is 100%, with the schema itself explaining that productId comes from list_products with examples. The description adds no format or constraint detail beyond what the schema already states, so the baseline of 3 applies.

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 and resource (get a product's captured flow) and enumerates exactly what is returned: ordered steps with title, notes, page url, observed transitions, alternate-branch flags, and handoffId. This is clearly a detail-fetch operation, distinguishable from the list_flows sibling without opening the 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?

Gives an explicit use case ("study how a product structures signup, onboarding or a task") and routes to a named follow-up (get_screen_image on steps you will copy). It lacks an explicit exclusion such as "use list_flows to enumerate flows first", but the intended context is clear.

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?