Skip to main content
Glama

Search Sections

search_sections
Read-only

Search 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for paginating through results.
limitNoMaximum number of sections to return. Higher number of sections returned causes increased context usage.
queryYesDescribe one website section in plain language, starting with what kind of section it is ("pricing section", "footer"). Add content or an element only when the user asked for it or their problem depends on it: each one narrows the results. Good: "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_toolNoThe 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_intentNoOne 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_formatNoImage format. Use jpg if your client does not support webp.webp
output_destinationNoWhat 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

TableJSON Schema
NameRequiredDescriptionDefault
pageYes1-based page number of this batch of search results.
queryYesThe natural language query used for this search.
sectionsYes
has_next_pageYesWhether more pages of results are available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Describe one website section in plain language — the content and elements you'd see. Be specific; detail helps. Good: \"pricing page with plan comparison table\", \"hero section with signup form\". Avoid: combining multiple sections (search separately), negations, vague style words, disconnected keyword lists."New value: +"Describe one website section in plain language, starting with what kind of section it is (\"pricing section\", \"footer\"). Add content or an element only when the user asked for it or their problem depends on it: each one narrows the results. Good: \"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."
  2. Changed2 schema fields changed
    • changedInput schema / properties / output_destination / description
      Previous value: -"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."New value: +"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."
    • changedInput schema / properties / output_tool / description
      Previous value: -"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."New value: +"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."
  3. Changed2 schema fields changed
    • 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"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / properties / sections / items / properties / image_url / description
      Previous value: -"Image URL for the section. 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."
  5. Changed1 schema field changed
    • 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."
  6. Changed1 schema field changed
    • 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"
      +}
  7. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare it a safe read (readOnlyHint=true, destructiveHint=false), and the description adds substantial context on top: results return images inline plus metadata, inline previews are low-res and meant for the model, image_url is the high-res asset, URLs expire after 30 days so files must be downloaded rather than linked, and hosts with MCP Apps render a gallery. This is exactly the beyond-annotations disclosure the dimension rewards.

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 in the first sentence, and subsequent sentences are functional rather than filler. It is comparatively long for a search tool, but nearly every sentence (image handling, expiry, citation) carries operational weight, so it stays on the right side of verbose.

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 7-parameter tool with an output schema, the definition covers the missing behavioral layer: return shape, image resolution split, expiry, citation practice, and interactive rendering. Nothing an agent needs to call it and use its 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 already carries the parameter burden — including detailed guidance on query construction, output_destination semantics and enum meanings. The description adds no per-parameter meaning beyond that, so the baseline 3 applies; its image_url/expiry passages are about outputs, not inputs.

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 ("Search Mobbin for website sections") with concrete examples (About, Pricing, Footer) and the input modality (natural language). The resource type is inherently distinct from the siblings search_screens and search_flows, so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives rich guidance on how to consume results (examine inline images, download from image_url when saving, link to mobbin_url) but never states when to pick this tool over search_screens or search_flows, nor any exclusions. Usage is implied by the resource noun rather than stated, so this lands at minimum-viable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.