Skip to main content
Glama

Search designs

search_designs
Read-only

Lists designs in the NightMarquee library, with a title, tagline, category, a poster, a short preview clip, whether a starter pack exists and a live demo link for each. Filter by words, category, free or paid, and page through the results with the cursor. Use it to find a design before reading it with get_design. It needs no account; open says whether the connected account can read a design's build prompt. Each call shows the user its own picker, so search once with broad words rather than several narrow searches.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_designs"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoThe kind of design. Only `site` exists today; any other kind returns no designs.
tierNoOnly free designs, or only designs that need a plan.
limitNoHow many designs to return, 1 to 50. The default is 10.
queryNoWords to look for in a design's title, tagline, description, style keywords, category and the businesses it suits, such as restaurant, hotel or florist.
cursorNoThe `cursor` from the previous result, to read the next page.
categoryNoA category slug from the `categories` list of an earlier search. An unknown category returns no designs.

Output Schema

NameRequiredDescriptionDefault
itemsYes
totalYes
cursorYes
categoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / items / items / properties / hasStarter
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / items / items / properties / previewUrl
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
      -  "slug",
      -  "kind",
      -  "title",
      -  "tagline",
      -  "category",
      -  "tier",
      -  "open",
      -  "posterUrl",
      -  "demoUrl"
      -]New value: +[
      +  "slug",
      +  "kind",
      +  "title",
      +  "tagline",
      +  "category",
      +  "tier",
      +  "open",
      +  "posterUrl",
      +  "previewUrl",
      +  "hasStarter",
      +  "demoUrl"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Words to look for in a design's title, tagline, description, style keywords and category."New value: +"Words to look for in a design's title, tagline, description, style keywords, category and the businesses it suits, such as restaurant, hotel or florist."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: no authentication required, the `open` flag reveals whether the connected account can read a design's build prompt, and each call renders a picker to the user — a side effect not captured by annotations. Listing the return fields is somewhat redundant given the output schema.

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?

It is front-loaded with the purpose and return shape, then usage, then behavioral caveats — a sensible order with no filler sentences. The enumeration of return fields is mildly redundant against the existing output schema and costs a few words.

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 six-parameter read-only search with full schema coverage, annotations, and an output schema, the description covers the remaining gaps an agent needs: auth requirement, pagination via cursor, the meaning of the `open` field, and the picker UI side effect. Nothing required to call it correctly 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 every parameter is already documented in the schema with constraints and defaults. The description only restates the filter axes (words, category, free/paid, cursor paging) and omits the `kind` and `limit` parameters entirely, adding little meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 opens with a specific verb and resource ("Lists designs in the NightMarquee library") and enumerates the returned fields, so an agent knows exactly what it gets. It also explicitly contrasts with the sibling get_design ("find a design before reading it with get_design"), which removes ambiguity between search and detail retrieval.

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

Usage Guidelines5/5

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

It states the use case ("find a design before reading it with get_design"), the precondition ("needs no account"), and an explicit anti-pattern ("search once with broad words rather than several narrow searches"). The alternative tool is named with the condition that selects it.

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.