Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Resize a static ad for other placements

resize_ad

Recompose a finished static ad natively for new aspect ratios, preserving copy, product, logo, and style instead of cropping it. Provide the ad image and target canvases to generate each placement.

Instructions

Re-lay out ONE finished static ad for other placements: the same ad, product, copy (word for word), logo and style, recomposed natively for each canvas rather than cropped. Pass image and optionally aspectRatios from 1:1, 4:5, 9:16, 16:9, 3:4, 4:3 (default 1:1, 4:5 and 9:16; the ad's own ratio is skipped). Reads the ad's text first (3 credits) so every line survives, then one image edit per canvas. When the saved brand has a product photo and the ad shows that product, the photo rides with the edit and the product's label is read and checked against it: re-printed from the photo only when it came out wrong (the check alone is charged when it is right; one small extra charge finds the product first). fixLabel:false turns that off. Priced before it runs. For VIDEO use reframe_video.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYesthe finished static ad: URL, Library item URL, upload_file URL or local path
fixLabelNofalse = leave the product label exactly as rendered: no product lookup, no label check, no re-print (default on when the ad shows the brand’s saved product)
aspectRatiosNotarget canvases (default 1:1, 4:5, 9:16)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.366
    • addedInput schema / properties / fixLabel
      Added value: +{
+  "description": "false = leave the product label exactly as rendered: no product lookup, no label check, no re-print (default on when the ad shows the brand’s saved product)",
+  "type": "boolean"
+}
  2. Addedv0.1.272

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare non-read-only, open-world, non-idempotent, non-destructive, and the description goes well beyond them: credit costs (3 credits for text read, one image edit per canvas, label-check and product-lookup charges), the fact it is priced before running, the sequencing of text extraction before edits, and the conditional product-photo behavior. This is unusually rich disclosure of side effects and cost.

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 purpose and the video exclusion, and every clause carries information. Some sentences are heavily parenthetical and dense ('the check alone is charged when it is right; one small extra charge finds the product first'), which costs readability but not correctness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter, no-output-schema tool, the description covers cost, defaults, conditional behavior, and the video alternative. The one gap is that with no output schema it does not state what is returned (e.g., rendered image assets), leaving the agent to infer the result shape.

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 real semantics beyond the schema: the default set of ratios, that the source ratio is skipped, and the conditional default-on behavior of the label fix tied to the saved brand product. It does not, however, add format detail like allowed input image types beyond what the schema lists.

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 verb and resource ('re-lay out ONE finished static ad for other placements') and immediately disambiguates the operation from cropping by describing native recomposition. It also separates itself from the video sibling by naming reframe_video. An agent can identify what this does without opening the 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?

Explicitly routes the agent away from this tool for video ('For VIDEO use reframe_video') and states the alternative-ratio condition (the ad's own ratio is skipped). It also gives the opt-out condition for the label workflow via fixLabel:false, covering both when-to-use and when-to-disable.

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