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. 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
`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 Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	The natural language query used for this search.
`screens`	Yes

TDQS

A4.5/5.0

Behavior5/5

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

Even with readOnlyHint=true and destructiveHint=false, the description adds significant behavioral value: it instructs the agent to examine returned images rather than inferring from metadata, mandates markdown citations to mobbin_url, and discloses the MCP Apps gallery rendering. These behaviors are not evident from annotations alone.

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?

The description is front-loaded with the core purpose and return value, then efficiently adds the most important usage constraints. Each sentence earns its place: the image-examination rule, the mobbin_url citation requirement, and the gallery rendering note are all materially useful without redundancy.

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 search tool with a rich input schema, a declared output schema, and read-only annotations, the description covers the essential behavioral guidance an agent needs: how to interpret results, how to cite them, and how the mode parameter affects latency/relevance. No critical calling detail 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?

Schema description coverage is 100%, so the schema already thoroughly documents all seven parameters, including enums, defaults, and constraints. The description reinforces query best practices but does not add new parameter-level meaning beyond what the schema already provides; baseline 3 is appropriate.

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?

The description states a specific verb ('Search'), a clear resource ('Mobbin UI screens'), and a distinct deliverable ('matching screens with inline images and metadata'). The name and phrasing clearly distinguish it from siblings like search_flows and search_sections by focusing on individual screens rather than flows or sections.

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?

The description gives clear context for when to use this tool: when searching for UI screens by natural language, and it includes detailed query guidance such as avoiding combined intents and negations. It does not explicitly mention alternatives like search_flows or search_sections, so it stops short of full when/when-not differentiation.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool searches a distinct content type—flows, screens, and sections—so an agent can clearly choose based on what kind of result is needed. The entity types are separate enough that there is no meaningful overlap or ambiguity.

Naming Consistency5/5

All three tools follow the exact same search_<plural-noun> pattern. This is a perfectly consistent and predictable naming convention.

Tool Count5/5

Three tools is well-scoped for a search-only server. Each tool covers one core Mobbin content category, and none feel redundant or unnecessary.

Completeness5/5

The server's apparent purpose is to search Mobbin's design content, and it covers the three primary content types: flows, screens, and sections. There are no obvious missing operations for this read-only search domain.

Resources

Need Help?