Search Sections
search_sectionsSearch Mobbin for website sections (e.g. About, Pricing, Footer) using natural language. Returns section images inline along with metadata. Examine the returned images to understand each section's actual content — do not describe or summarize sections 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>"
},
"name": "search_sections"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for paginating through results. | |
| limit | No | Maximum number of sections to return. Higher number of sections returned causes increased context usage. | |
| query | Yes | Describe one website section in plain language: what kind of section it is ("pricing section", "footer"), with the kind of product when the user names one ("banking app", "developer tool"). The kind of product is part of the request, so include it in the query. Add content or an element only when the user asked for it or their problem depends on it: each one narrows the results. Good: "AI tools pricing section", "hero section with signup form". Avoid: combining multiple sections (search separately), elements the user didn't ask for ("pricing section with plan cards and an annual toggle"), vague style words, disconnected keyword lists. | |
| 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 this batch of search results. | |
| query | Yes | The natural language query used for this search. | |
| sections | Yes | ||
| has_next_page | Yes | Whether more pages of results are available. |