Skip to main content
Glama

creative_studio_generate_visual

Generate text-free key-visual PNGs for ad creatives, automatically appending a no-text constraint to the prompt. Supports multiple providers, aspect ratios, and layout templates for later text 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.
Behavior4/5

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

With no annotations, the description covers key behavioral traits: images are saved to a new run directory with provenance manifest.json, returns run id, directory, file paths with SHA-256. It also mentions the hard no-text constraint applied automatically.

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 four sentences, each serving a distinct purpose: purpose, prompt constraint, output details, provider usage. It is concise and front-loaded.

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?

Given the tool has 5 parameters with 100% schema coverage and no output schema, the description provides sufficient context about the output structure and key behavior. Some nuance about template is only in schema, but overall complete.

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%, and the description adds value beyond schema by emphasizing that prompts must be imagery-only and that a no-text constraint is appended. It also clarifies the 'all' option for provider.

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 it generates text-free key-visual PNGs for ad creative, distinguishing it from siblings like creative_studio_compose (which likely adds text) and creative_studio_edit_visual. It specifies the output format and purpose.

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 explains when to use it (for imagery-only prompts) and how to use provider parameter ('all' to fan out). It does not explicitly state when not to use or alternatives, but the context is clear.

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