Skip to main content
Glama
hermoso-ai

Hermoso

Official

Generate ad image

generate_image

Render ad images with product-accurate compositing using refImages. Supports brand hydration and custom prompts for multi-brand use.

Instructions

Render a finished ad IMAGE and return its served URL. refImages (local paths or URLs) force product-accurate compositing (drops a real product into the scene). MULTI-BRAND CAUTION: useBrand hydration pulls the SAVED workspace brand — when working a brand that is NOT the saved one (a fresh draft_brand), pass that brand's own productImages/logo as refImages (and useBrand:false) or the output composites the WRONG brand's product. model = a catalog id from hermoso_capabilities (omit for the default). Fast (seconds). Spends credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoimage model id from hermoso_capabilities
promptYesthe full image prompt — subject, composition, lighting, and any on-image ad text
useBrandNodefault true: with no refImages, the server hydrates the SAVED brand’s product/logo references so the output lands on-brand; pass false for a pure prompt-only render
imageSizeNopixel-size preset for models that support it (e.g. 1K/2K) — omit for the default
refImagesNolocal file paths or URLs of product/logo references to composite in
aspectRatioNoe.g. '1:1', '9:16', '16:9'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageNothe served absolute URL of the finished image
modelNothe product-facing label of the model that rendered it
Behavior5/5

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

Adds behavioral details beyond annotations: 'Fast (seconds)', 'Spends credits', and explains how refImages and useBrand affect output. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence earns its place. Front-loaded with primary purpose, followed by critical warnings and parameter context. No waste.

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?

Comprehensive given 6 params, 1 required, 100% schema coverage, and output schema exists. Covers speed, credits, multi-brand handling, and parameter nuances.

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%, baseline 3. Description adds meaning by explaining the interplay of useBrand and refImages, and clarifying that model can be omitted for default. Adds context beyond schema.

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 'Render a finished ad IMAGE and return its served URL' with a specific verb and resource, and distinguishes itself from siblings like render_ad by emphasizing compositing with refImages and multi-brand handling.

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?

Provides explicit guidance: when to use refImages with useBrand:false for non-saved brands, and mentions model from hermoso_capabilities. The MULTI-BRAND CAUTION is a clear when-not-to-use warning.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hermoso-ai/hermoso'

If you have feedback or need assistance with the MCP directory API, please join our Discord server