Skip to main content
Glama

List Designs

list_designs
Read-onlyIdempotent

Browse Zarla's marketplace designs (1,200+) — the looks a site can be moved onto with switch_design. Pass site_id to put designs made for that site's industry first (for_your_business: true). Narrow by look (bold, modern, professional, elegant, friendly, warm, luxury, playful), by industry (slug or name) or with a search query; paged 20 at a time (max 50) via offset. Each design carries the schema_key that switch_design takes. For colors/fonts only, use update_design instead — no design change needed.

Annotations: read-only=true, destructive=false, idempotent=true, open-world=false. Why: Reads data only and changes nothing (read-only, so trivially idempotent). Closed-world: it touches only Zarla's own database.

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": "list_designs"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookNoFilter by look
limitNo
queryNoSearch industry names, keywords and design names
offsetNo
site_idNoOrder designs for this site's industry first
industryNoIndustry slug or name (see list_industries)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: page size is 20 (max 50) via offset, and each result carries the schema_key that switch_design consumes, which tells the agent how to chain calls. It stops short of describing result ordering beyond the site_id case or total-count behavior.

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?

Front-loaded with purpose and the sibling relationship before filters and pagination details. It is a single dense paragraph with semicolon-separated clauses; a small amount of repetition of schema values keeps it slightly longer than necessary but nothing is wasted.

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, optional-only filtering list tool with no output schema, the description covers scope, prioritization, filtering axes, pagination limits, downstream use of schema_key, and the alternative sibling. An agent has everything needed to call it correctly on the first try.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is moderate (67%), but the description compensates: it explains that site_id produces a 'for_your_business: true' flag (not documented in the schema), that industry accepts slug or name, and that query searches industry names, keywords and design names. Some redundancy exists (repeating the look enum and the 50 max), but the added meaning is real.

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 ('Browse Zarla's marketplace designs') and immediately scopes it against a sibling: 'the looks a site can be moved onto with switch_design.' An agent can distinguish this from switch_design and update_design without opening any schema.

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?

Gives explicit when-to-use guidance (pass site_id to prioritize the site's industry, narrow by look/industry/query) and an explicit when-not/alternative: 'For colors/fonts only, use update_design instead — no design change needed.' Routing to list_industries is also implied by the industry parameter description.

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.