Mobbin

Search Screens

search_screens

Read-only

Search Mobbin for UI screens using natural language. Returns matching screens with inline images and metadata. Examine the returned images to understand each screen's actual content — do not describe or summarize screens based solely on metadata. Each screen has a mobbin_url — the canonical Mobbin link for that screen. When you present results to the user, ALWAYS cite each screen you mention as a markdown link to its mobbin_url so the user can open it on Mobbin. 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. If the result contains ai_usage_notice, show its markdown to the user word for word, as its own block after the results, keeping its formatting and line breaks. Do not paraphrase, shorten, or merge it with other text. On hosts that support MCP Apps, also renders an interactive gallery of the results.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Search mode. "standard" returns results with low latency. "deep" uses an AI-powered pipeline that interprets intent and scores each candidate for relevance, keeping the strong matches — ideal for nuanced queries. "fast" is a deprecated alias for "standard" and will be removed in a future version — use "standard" instead.	deep
`limit`	No	Maximum number of screens to return. Higher number of screens returned causes increased context usage.
`query`	Yes	Describe one screen in plain language — the UI elements you'd see and how they relate. Be specific; detail helps. Good: "login screen with biometric authentication", "checkout page with promo code field and Apple Pay button". Avoid: combining multiple screens/intents (search separately), negations ("without ads"), vague style words ("modern", "clean"), disconnected keyword lists. Name a specific app to filter results to it (e.g. "Spotify now-playing screen"). 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, 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
`exclude_screen_ids`	No	Screen IDs to exclude from results
`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, 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

TableJSON Schema

Name	Required	Description
`query`	Yes	The natural language query used for this search.
`screens`	Yes
`ai_usage_notice`	No	Present only when the user's AI usage is high. Show this markdown to the user word for word after presenting the results, keeping its formatting and line breaks.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

addedOutput schema / properties / ai_usage_notice

Added value: +{
+  "description": "Present only when the user's AI usage is high. Show this markdown to the user word for word after presenting the results, keeping its formatting and line breaks.",
+  "type": "string"
+}

Changed2 schema fields changedSep 24, 2026

addedInput schema / properties / output_destination

Added value: +{
+  "description": "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, 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.",
+  "enum": [
+    "code",
+    "design_tool",
+    "doc",
+    "reference_library",
+    "chat",
+    "other"
+  ],
+  "type": "string"
+}

addedInput schema / properties / output_tool

Added value: +{
+  "description": "The product the results go into next, 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.",
+  "type": "string"
+}

Changed1 schema field changedSep 15, 2026

changedOutput schema / properties / screens / items / properties / image_url / description

Previous value: -"Image URL for the screen. Expires after 30 days."New value: +"High-resolution image URL (up to 1920px wide). Download from it whenever the user wants to save, export, embed, or paste the image. Expires after 30 days."

Changed1 schema field changedAug 28, 2026

changedInput schema / properties / task_intent / description

Previous value: -"One short sentence summarizing the user's overall task. Helps return more relevant results. MUST be the same across all calls for the same task. Do NOT include verbatim user messages, conversation history, file contents, or personal data."New value: +"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."

Changed1 schema field changedAug 27, 2026

addedInput schema / properties / task_intent

Added value: +{
+  "description": "One short sentence summarizing the user's overall task. Helps return more relevant results. MUST be the same across all calls for the same task. Do NOT include verbatim user messages, conversation history, file contents, or personal data.",
+  "type": "string"
+}

First observedAug 18, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover the read-only/safe profile, and the description adds substantial operational traits beyond them: inline images are low-res previews while image_url is high-res, URLs expire after 30 days, ai_usage_notice must be reproduced verbatim, and an interactive gallery renders on MCP Apps hosts.

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?

Purpose is front-loaded, but the body is dense with presentation/download instructions that occasionally restate the same point (expiration and download-vs-link appear twice). Most sentences earn their place, but it is longer than strictly necessary.

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?

With an output schema covering return values and annotations covering safety, the description still supplies the missing operational layer: image handling, citation format, and notice reproduction. Nothing an agent needs to call and present results correctly is absent.

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 description coverage is 100%, so the schema itself fully documents all nine parameters (mode, limit, query, platform, output_tool, output_destination, etc.). The description adds little parameter-specific meaning, so the baseline 3 applies.

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 ('Search Mobbin for UI screens using natural language') and describes the return ('matching screens with inline images and metadata'). It clearly differs from search_flows/search_sections by resource type, though it never names those siblings to sharpen the distinction.

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?

Offers rich guidance: how to phrase queries (avoid negations, multi-screen intents, vague style words), when to download from image_url vs link mobbin_url, and when to display ai_usage_notice. It stops short of explicit tool-selection guidance against search_flows/search_sections.

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

All Mobbin tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.