Skip to main content
Glama

Browse Fashio's ready-made photoshoot library

list_ready_template_sets

Browses Fashio's own curated 'ready photoshoot' library (each set = one model + one venue + several pinned shots) and returns {templateSets: [{id, displayNames, description, coverUrl, tags, shotCount, isFeatured, shots: [{id, shotType, framing, previewUrl, thumbUrl, isDefault}]}], nextCursor}. Use it to pick a readyTemplateSetId for create_catalog_job when you have no styling of your own; use list_template_sets instead for presets you saved yourself. Paged: up to limit sets per call; pass nextCursor back as startAfter (same sort and filters) for the next page, and nextCursor null means the last page. Filters are exact tag matches combined with AND (the values appear in each set's tags). Free (no diamonds). Needs a valid Fashio API key (Bearer); every call counts toward the key's daily request cap (429 when reached, 401 for a missing or revoked key).

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_ready_template_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNoMood tag, e.g. clean_commerce, quiet_luxury, graphic_editorial, warm_resort, raw_street, romantic_soft.
sortNocurated (default, Fashio's editorial order), popular (most used first) or newest (most recently added first).
typeNoSet type tag: catalogue | single.
limitNoSets per page, 1-60 (default 20).
queryNoOne search keyword, matched case-insensitively as a whole term against each set's search terms (not fuzzy). Ignored when category is set.
genderNoGender tag, e.g. women, men, unisex, kids.
paletteNoColour palette tag, e.g. neutral_greige, monochrome_white, warm_terracotta, cool_concrete, bold_saturated, earth_tone.
settingNoSetting tag, e.g. studio_seamless, studio_cyclorama, outdoor_street, outdoor_beach, interior_home, poolside.
categoryNoGarment category tag, e.g. resortwear, tailoring, outerwear, knitwear, streetwear, denim, activewear, eveningwear, basics.
lightingNoLighting tag, e.g. soft_diffused, golden_hour, flat_ecommerce, hard_sun, moody_directional.
startAfterNoThe nextCursor value from the previous page's response; omit for the first page. Keep the same sort and filters across pages.
featuredOnlyNotrue = only sets Fashio marks as featured. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Garment category tag, e.g. resortwear, tailoring, outerwear, knitwear, streetwear, denim, activewear, eveningwear, basics."
    • addedInput schema / properties / featuredOnly / description
      Added value: +"true = only sets Fashio marks as featured. Default false."
    • addedInput schema / properties / gender / description
      Added value: +"Gender tag, e.g. women, men, unisex, kids."
    • addedInput schema / properties / lighting / description
      Added value: +"Lighting tag, e.g. soft_diffused, golden_hour, flat_ecommerce, hard_sun, moody_directional."
    • addedInput schema / properties / limit / description
      Added value: +"Sets per page, 1-60 (default 20)."
    • addedInput schema / properties / mood / description
      Added value: +"Mood tag, e.g. clean_commerce, quiet_luxury, graphic_editorial, warm_resort, raw_street, romantic_soft."
    • addedInput schema / properties / palette / description
      Added value: +"Colour palette tag, e.g. neutral_greige, monochrome_white, warm_terracotta, cool_concrete, bold_saturated, earth_tone."
    • changedInput schema / properties / query / description
      Previous value: -"Free-text search."New value: +"One search keyword, matched case-insensitively as a whole term against each set's search terms (not fuzzy). Ignored when category is set."
    • addedInput schema / properties / setting / description
      Added value: +"Setting tag, e.g. studio_seamless, studio_cyclorama, outdoor_street, outdoor_beach, interior_home, poolside."
    • addedInput schema / properties / sort / description
      Added value: +"curated (default, Fashio's editorial order), popular (most used first) or newest (most recently added first)."
    • changedInput schema / properties / startAfter / description
      Previous value: -"Cursor from the previous page's response."New value: +"The nextCursor value from the previous page's response; omit for the first page. Keep the same sort and filters across pages."
    • addedInput schema / properties / type / description
      Added value: +"Set type tag: catalogue | single."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that the call is free (no diamonds), that it requires a Bearer API key, that every call counts toward a daily request cap, and it names the 429 and 401 failure modes. It also explains pagination semantics (nextCursor null means last page) and that filters combine with AND.

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-loads purpose, then usage routing, then pagination, cost, and auth — a sensible ordering with little waste. It is a dense single paragraph and the inline return-shape enumeration is heavy, but every sentence conveys actionable information.

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 12-parameter, read-only listing tool with no annotations or output schema, the description covers cost, auth, rate limits, pagination, filter semantics, and return shape. An agent could invoke and page through this tool correctly without any further information.

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 100%, so the baseline is 3; the description adds genuine meaning by explaining that filters are exact tag matches combined with AND and that matching values appear in each set's `tags`, and by tying nextCursor to the startAfter parameter with the same sort and filters. It does not restate individual filter values, which is correct since the schema already does.

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 ("Browses Fashio's own curated 'ready photoshoot' library"), defines what a set contains, and even enumerates the return shape. It is unmistakably distinct from list_template_sets and get_ready_template_set.

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 an explicit selection rule: use this to obtain a readyTemplateSetId for create_catalog_job when you have no styling of your own, and use list_template_sets for your own saved presets. Both the when and the when-not are named with the alternative sibling.

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.