Skip to main content
Glama
hermoso-ai

Hermoso

Official

Plan an ad concept

plan_ad

Take a brand and product brief, and produce a complete ad concept with copy variants and a visual prompt for image or video generation.

Instructions

Creative director: turn a brand + product/brief into a finished ad CONCEPT — copy variants (headline/primary/cta) plus an image_concept.prompt OR a video_storyboard, with the resolved recipe + the model ids to render with. Renders nothing; chain its output into generate_image / generate_video. Spends LLM tokens, 0 ScrapeCreators credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandNobrand name, or a brand profile object {name,domain,category,palette,products,…}. OMIT to use the workspace’s SAVED brand + memory automatically (see get_brand); use draft_brand to onboard a new one
formatNo'image', 'video', or 'auto' when unspecified
recipeNoa recipe id from hermoso_capabilities to force an archetype
productYeswhat to advertise + any angle/offer the user specified
languageNooutput language for the ad copy (e.g. Spanish) — default English
referenceNoa reference ad URL to remix the angle from — Facebook Ad Library, LinkedIn Ad Library or Google Ads Transparency links (the real ad’s copy/advertiser are fetched and fed into the concept)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
copyNocopy variants ({headline, primary, cta})
brandNothe brand grounding embedded in the creative (name, logo, palette, productImages)
formatNothe resolved creative format — 'image' or 'video'
imodelNothe image model id to render with
recipeNothe resolved recipe id
vmodelNothe video model id to render with
conceptNothe one-line creative concept
render_planNothe routing plan (structure/duration) render_ad honors
recipe_labelNothe resolved recipe display name
image_conceptNothe render-ready image concept (prompt etc.) when format is image
video_storyboardNothe timed storyboard (scenes, cta, music) when format is video
Behavior4/5

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

Beyond annotations (which only hint at non-destructive behavior), the description discloses that the tool spends LLM tokens but no ScrapeCreators credits. It also clarifies that it does not render anything, adding behavioral context. However, it does not detail error handling or side effects beyond creation.

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?

The description is concise with no redundant words. It uses a clear subject line and efficiently conveys key information in a few sentences, making it easy to parse.

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?

Given the tool's complexity (6 parameters, output schema exists), the description covers purpose, usage, cost, and chaining. It is complete enough for an agent to understand when and how to invoke it.

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?

The description adds value beyond the schema by explaining when to omit brand, how product should include angle/offer, and the nature of reference ads. Schema coverage is 100%, but the additional context enhances usability.

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 clearly states the tool's purpose: turning a brand and product into a finished ad concept with copy variants and an image or video prompt. It distinguishes itself from sibling tools by explicitly stating it renders nothing and should be chained with generate_image/generate_video.

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 provides context on when to use the tool, such as chaining with generation tools and opting to omit the brand parameter to use a saved brand. It lacks explicit when-not-to-use scenarios but offers sufficient guidance for typical use.

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