Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Set product photo

set_product_image
Idempotent

Lock a product image as your brand's default photo so every future ad render uses the true packaging. Pass an image URL; it validates, saves durably, and confirms the brand state.

Instructions

Lock an image as the ad's real PRODUCT photo and SAVE it as this brand's default product, so every later plan_ad / render_ad / generate_image grounds on the true packaging without being told again. Pass imageUrl = a product shot's URL — an image from a prior research result (an organic Instagram/TikTok post, a scraped page image), a workspace / list_product_photos url, or any public product photo. The server downloads it and runs a product+safety check: a lifestyle/scene shot with no clear product, or an off-category / unsafe image, is REJECTED and NOTHING is locked or saved (the summary says why). On PASS it persists the photo to a DURABLE url, writes it to the brand's product library as the DEFAULT, and READS THE BRAND BACK to confirm — savedToBrand and the summary report what the brand ACTUALLY holds now, never what was asked for, so if it did not become the default you are told instead of finding out from a paid render. Bills one vision check. Reads YOUR saved brand for the category match (pass brandId to target a specific brand — switches this key's active brand like use_brand).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandIdNoa brand id/name from list_brands to lock the product for; omit to use the active brand
imageUrlYesthe image URL to lock as the product (from a research result, a workspace / list_product_photos url, or any public product photo)
source_noteNoa short note on where it came from, e.g. "from their IG post"

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": {
-    "attached": {
-      "description": "true when the image passed the product check and was locked",
-      "type": "boolean"
-    },
-    "source_note": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "where the photo came from"
-    },
-    "summary": {
-      "description": "the check verdict — on rejection, why nothing was locked",
-      "type": "string"
-    },
-    "url": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "the durable served URL of the locked product photo"
-    }
-  },
-  "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?

The description goes far beyond the annotations, disclosing that the server downloads the image, runs product and safety checks, rejects unsuitable images with nothing locked or saved, persists to a durable URL, reads the brand back to confirm, and reports actual state rather than requested state. It also mentions billing one vision check and active-brand switching 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?

The description is long but dense and front-loaded with the core purpose. Every sentence carries relevant behavioral or usage information, from rejection conditions to confirmation behavior and billing. It is not minimalist, but the length is justified by the tool's complexity and the absence of an output schema.

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?

With no output schema, the description adequately explains what the caller can expect: savedToBrand and a summary that reflect the actual brand state, explicit failure behavior, persistence, and the confirmation read-back. Given the tool's side effects and integration with other ad tools, this is complete enough for an agent to invoke and interpret the result correctly.

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 baseline is 3, but the description adds meaningful detail: imageUrl is expanded to include research results, organic post images, workspace/list_product_photos URLs, and public product photos; brandId is explained as targeting a brand and switching the active brand. source_note is not given extra meaning, but two of three parameters are enriched.

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 states a specific verb and resource: 'Lock an image as the ad's real PRODUCT photo and SAVE it as this brand's default product.' It clearly differentiates from sibling tools like list_product_photos and use_brand by explaining that this tool sets the persistent default product photo used by later ad-generation tools.

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?

The description gives clear context for when to use the tool: before plan_ad/render_ad/generate_image to establish the true product packaging, and it explains how brandId targets a specific brand, even noting it switches the active brand 'like use_brand.' It does not explicitly state when not to use it or name direct alternatives, but the usage 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