Skip to main content
Glama

creative_studio_generate_visual

Generate text-free key-visual images for ad creatives, enforcing no-text automatically, and return run ID, paths, and SHA-256 checksums for later typography overlay.

Instructions

Generate text-free key-visual PNGs for an ad creative. The prompt describes the imagery ONLY — headline/body/CTA text is added later by the typography layer, so a hard no-text constraint is appended automatically. Images are written to a new run directory with a provenance manifest.json; the tool returns the run id, directory, file paths (with SHA-256), and manifest path. Use 'provider' to pick one configured provider, or 'all' to fan out one image per configured provider.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNoNumber of candidate images to generate.
aspectNoMaster aspect class; picks the recommended generation size.square
promptYesDescription of the VISUAL only (scene, subject, style, mood). Do not include any copy/text to render.
providerNoProvider name to use (defaults to the first configured provider). Pass 'all' to generate one image per configured provider.
templateNoLayout template you intend to compose with. When set, a precise negative-space sentence is appended to the prompt so the subject leaves the calm zone that template overlays copy into (hero_overlay -> lower third clear; split -> one half clear; minimal_badge -> even center-weighted texture). Omit to add nothing.
Behavior5/5

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

With no annotations provided, the description fully carries the burden. It discloses the automatic no-text constraint, writes to a new run directory with a provenance manifest.json, and specifies return values including run id, directory, file paths with SHA-256, and manifest path. This exceeds basic expectations.

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?

Three dense sentences convey purpose, constraints, file output, return payload, and provider behavior without any filler. The structure is front-loaded with the core action and progresses logically through output and usage details.

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 5-parameter tool with no output schema, the description covers return values, side effects (file writing), provider behavior, and template-specific prompt modifications. It also acknowledges the typography pipeline context, making it complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with every parameter (n, aspect, prompt, provider, template) documented. The description adds emphasis on the prompt being visual-only and the template's negative-space behavior, but these are largely redundant with the schema descriptions. Baseline 3 is appropriate.

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 opens with a specific verb+resource: 'Generate text-free key-visual PNGs for an ad creative.' It clearly differentiates from siblings like creative_studio_edit_visual by noting text is added later by the typography layer, and it explains the tool's role in the pipeline.

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?

It provides clear context for when to use the tool (creating text-free key visuals) and describes provider selection, including the 'all' fan-out option. It does not explicitly name alternatives like creative_studio_edit_visual or creative_studio_compose, but the usage context is well-defined.

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/logly/mureo'

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