Search Flows
search_flowsSearch Mobbin for multi-step user flows (e.g. onboarding, checkout) using natural language. Returns evenly-spaced preview images inline along with metadata for each flow, including per-screen previews. Examine the returned images to understand each flow's actual content — do not describe screens based solely on metadata. Inline images are low-res previews for you to read, not for the user. Each result's image_url is the high-resolution image. Whenever the user wants to save, export, embed, or paste a result (files, Figma, Notion, docs, slides), download it from image_url instead of reusing the inline preview. Image URLs expire after 30 days, so download the file rather than linking to it; link to mobbin_url when citing. On hosts that support MCP Apps, also renders an interactive gallery of the results.
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": {
"query": "<query>",
"platform": "<platform>"
},
"name": "search_flows"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for paginating through results. Maximum 20. | |
| limit | No | Maximum number of flows to return. Lower limits are recommended to manage context size. | |
| query | Yes | Describe one user journey in plain language: what kind of journey it is ("onboarding", "password reset"), with the kind of app when the user names one ("banking app", "fitness app"). The kind of app is part of the request, so include it in the query. Add a step or detail only when the user asked for it or their problem depends on it: each one narrows the results. Good: "banking app onboarding", "checkout with payment method selection". Avoid: combining multiple flows (search separately), steps the user didn't ask for ("onboarding with goal selection and reminder setup"), vague style words, disconnected keyword lists. Name a specific app to filter results to it (e.g. "Duolingo onboarding"). Do not include platform (ios/web) — use the dedicated parameter. | |
| platform | Yes | Platform to search. | |
| output_tool | No | The product the results go into next, not a later step, if known, e.g. Figma, Paper, Notion. Product name only. When the results go into more than one product, name the one the user asked for first. Not the search source: Mobbin only when the results go back to Mobbin. Omit when unknown. MUST be the same across all calls for the same task. | |
| task_intent | No | One short sentence summarizing the user's overall task. Helps return more relevant results. Write it in English even when the conversation is in another language. MUST be the same across all calls for the same task. Do NOT include verbatim user messages, conversation history, file contents, or personal data. | |
| image_format | No | Image format. Use jpg if your client does not support webp. | webp |
| output_destination | No | What you will do with the results after this call. Choose by what gets made with the results, not by the search itself. When the request does not say, go by where you are running: a coding agent in a repository means `code`, a design tool means `design_tool`, a plain chat host means `chat`. Helps return results in the form the workflow needs. `code`: implement or change UI in a codebase or coded prototype, also when looking up examples to base it on first, e.g. React, Swift, HTML/CSS, v0, Lovable. `design_tool`: recreate or put results on a design canvas, e.g. Figma, Paper, Pen.dev, MagicPath. `doc`: write a report, PRD, spec, audit or slides, e.g. in Notion, Google Docs or Slides. `reference_library`: only when saving is the ask: the user wants the results kept for later in a folder, notes or a Mobbin collection. Looking things up to build, design or write from is NOT this. `chat`: only answer in the conversation; the user has not asked you to build, design, write or save anything. `other`: an unlisted destination, none of the above, e.g. posting the results to Slack or email. MUST be the same across all calls for the same task. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | Yes | 1-based page number of search results. | |
| flows | Yes | ||
| query | Yes | The natural language query used for this search. | |
| has_next_page | Yes | Whether more pages of results are available. |