Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List product photos

list_product_photos
Idempotent

List product photos already saved in your brand library and app-store screens to reuse before setting an image. Returns each photo's URL and label; pass brandId to target a profile.

Instructions

List the product photos ALREADY saved in your workspace — the brand's product library plus any app-store screens (also surfaces photos locked in your OTHER creations, since a set product lands in the shared library). FREE — returns each photo's url + label. Call it before set_product_image to see the existing photos you can reuse. Reads YOUR saved brand (pass brandId to target a specific profile — that switches this key's active profile like use_brand).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandIdNoa profile id/name from list_brands whose product library to list; omit to use the active profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brandId / description
      Previous value: -"a brand id/name from list_brands whose product library to list; omit to use the active brand"New value: +"a profile id/name from list_brands whose product library to list; omit to use the active profile"
  2. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "photos": {
-      "description": "the saved photos ({url, label, …})",
-      "items": {},
-      "type": "array"
-    },
-    "summary": {
-      "description": "a readable rundown of the saved product photos",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial traits beyond annotations: the operation is 'FREE' (cost), the return payload is 'each photo's url + label', and critically that passing brandId 'switches this key's active profile like use_brand' — a state-mutating side effect that explains why readOnlyHint is false. This is exactly the kind of non-obvious behavior the description should disclose.

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 the core action and scope, then rationale and workflow in descending priority. The heavy parentheticals make it dense, but each clause conveys a distinct, useful fact rather than filler.

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 single optional-parameter tool with no output schema, the description covers what it returns (url + label), cost, the upgrade/scope behavior, and how it fits with set_product_image. Nothing an agent needs to invoke it correctly is missing.

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 schema already documents the parameter, making 3 the baseline. The description goes further by documenting the side effect of brandId (profile switching) and the fallback when omitted, adding meaning the schema does not carry.

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?

Names a specific verb and resource (list product photos) and precisely bounds the scope: brand product library, app-store screens, and photos from other creations landing in the shared library. This distinguishes it from siblings like list_library and fetch_app_screens without needing to open 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 workflow guidance: 'Call it before set_product_image to see the existing photos you can reuse,' naming the alternative tool and the ordering condition. It also states the argument choice (omit brandId for active profile) with the consequence of passing one.

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

Deploy Server

Other Tools