Skip to main content
Glama

Search inspiration galleries

inspo_search

Search design galleries for a query, download matching thumbnails to a board, and optionally screenshot top live sites for reference research.

Instructions

Search Awwwards, Dribbble, Land-book, One Page Love, Siteinspire, Lapa Ninja and Mobbin for a query, download the thumbnails and add them to the board. Run it several times with different, specific queries (industry, vibe, section type: "fintech dark 3d", "coffee editorial", "pricing page"). Optionally screenshot the live sites of the top 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": "inspo_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results per source (default 8).
queryYesShort search query in English. Galleries match on titles/tags, so 1-3 words work best.
sectionNoTag results as references for this page section.
sessionNoSession id. Defaults to the most recent session in this project.
sourcesNoDefault: awwwards, dribbble, landbook, siteinspire, onepagelove.
platformNoMobbin only. Default web.
captureLiveNoAlso screenshot + analyze the live site of the first N results that link to one (default 0; each takes ~10s).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that thumbnails are downloaded and written into the board (a mutation, not a read), and that captureLive triggers live-site screenshots at roughly 10s each. It omits auth requirements, rate limits, and what happens on a failed source, but the costly and state-changing behaviors are surfaced.

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?

Three sentences, front-loaded with the core action before the strategy advice and the optional add-on. The query examples justify their length because they teach the phrasing the galleries expect. Minor looseness in the long source list, which the schema already enumerates.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, no-annotation, no-output-schema tool, the description covers the two things an agent most needs to know: it writes into the board and captureLive is slow. It does not explain what searching returns (counts, image references, failures per source) or which board/session context is used by default, leaving a small gap.

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 explains query, limit, section, session, sources, platform, and captureLive. The description reinforces query phrasing with worked examples and clarifies that the screenshot behavior is optional, but adds little beyond the schema's own wording. Baseline 3 applies.

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 concrete verb and resource chain — search seven named galleries for a query, download thumbnails, add them to the board — plus the optional live-site screenshot. Naming the exact sources makes the scope unambiguous, and the mention of board insertion distinguishes it from a pure read/search.

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?

It gives explicit invocation strategy — run it several times with different, specific queries — and supplies concrete example queries keyed to industry, vibe, and section type, which is genuinely actionable guidance. It stops short of naming when to prefer a sibling (e.g. inspo_harvest or inspo_add_images) or when a single broad query is preferable.

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