Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List product photos

list_product_photos
Read-only

List saved product photos from your brand library, including app-store screens and images in other creations, to see reusable assets before setting a product image.

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 brand — that switches this key's active brand like use_brand).

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations mark readOnlyHint=true and destructiveHint=false, and the description adds valuable context: the call is FREE, returns each photo's url + label, reads the saved brand, and brandId switches the active brand. It also discloses the non-obvious shared-library behavior where photos from other creations surface.

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 information-dense sentences with the core purpose front-loaded and no filler. The parentheticals add useful detail but make the structure slightly dense.

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 simple read-only list tool with one optional parameter and no output schema, this description is complete: it specifies the return shape, brand selection behavior, when to call it, and the unusual visibility across creations. Nothing essential 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%, but the description goes beyond the schema by explaining the omit-vs-pass distinction for brandId and the active-brand switching side effect. This adds meaningful semantics that the schema alone does not convey.

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 precise operation: listing product photos already saved in the workspace, and further delimits the contents (brand product library, app-store screens, and photos from other creations). This clearly distinguishes it from related tools like set_product_image and list_library.

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?

Explicitly instructs the agent to call this before set_product_image to see reusable photos, and explains when to pass brandId versus omitting it to use the active brand. It does not name when-not-to-use conditions or alternatives, but the context is strong.

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