Skip to main content
Glama

generate_app_icon

Generates square, transparent 1024px PNG app icons and logos from a subject description. Enforces correct format for macOS, iOS, Android, and web use.

Instructions

═══════════════════════════════════════════════════════════════════════════════ 🍏 APP ICON & LOGO GENERATOR (square · transparent · ready for .iconset) ═══════════════════════════════════════════════════════════════════════════════

Use THIS tool — not generate_image — whenever the user asks for an app icon, application icon, .icns, .iconset, macOS/iOS/Android icon, favicon, logo, logomark, or brand mark. It is purpose-built for that job and removes every way to get it wrong.

🔒 WHAT IS FORCED (you cannot override these — by design): ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • TRANSPARENT background — ALWAYS. Every result is a real alpha-channel PNG cut-out. There is no opaque-background option, because an icon or logo with a baked-in rectangle behind it is wrong. The transparent file path comes back as "transparent_path". • 1:1 SQUARE — ALWAYS. Every app icon is square; there is no aspect-ratio knob to get wrong. • 1K (1024px) — ALWAYS. This is the master size every .iconset slice and store listing is downscaled from. • PNG — ALWAYS. The lossless alpha format icons ship in. • CUT-OUT ONLY — ALWAYS. Only the transparent PNG is written; the pass-1 (white-background) original is never kept.

⛔ HOW TO WRITE THE PROMPT (READ THIS — the tool enforces it): ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ This tool IS the app-icon maker. Your prompt must describe ONLY the subject/artwork — NOTHING about the deliverable. Do NOT write "app icon", "application icon", "make an icon of", "logo of", "squircle", or anything about output/format/shape. The tool turns your subject INTO the icon.

WRONG: "an app icon of a blue magnifying glass over a network" RIGHT: "a glowing electric-blue magnifying glass over a network graph"

If your prompt contains "app icon", "logo", "favicon", "squircle" (or similar framing), the tool will REJECT the call and make you rewrite it. Just describe the picture.

The ONLY exception is when one of those words is genuinely PART OF THE SUBJECT you are depicting — e.g. a neon sign that literally reads "LOGO", or a picture OF a favicon. In that rare case, set allow_icon_words_in_prompt=True to bypass the check. Do NOT use it just to sneak deliverable-framing past the guard.

📋 PARAMETERS (what you DO control): ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ► prompt (required, str): Describe ONLY the subject/artwork itself — see the rule above. Don't ask for a background, a rectangle, a drop shadow, or a presentation surface. A bold, simple, single focal form reads best at small sizes.

► reference_image_paths (optional, str | list[str]): Brand/style reference image path(s), up to 14 (e.g. an existing logomark or palette to stay consistent with).

► enable_google_search / enable_image_search (optional, bool): Ground the design in real brand/product references found on the web.

► thinking_level (optional, str, default: "high"): "minimal" or "high". Defaults to "high" — icons reward the extra composition reasoning.

► allow_icon_words_in_prompt (optional, bool, default: False): Escape hatch for the prompt guard. Leave False. Set True ONLY when a word like "logo"/"favicon" is literally part of the subject you are depicting (e.g. a neon sign reading "LOGO"), not framing of the deliverable. Misusing this to bypass the guard defeats the point.

📤 RESULT / NEXT STEPS: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Use result["images"][0]["transparent_path"] — that is the square, transparent 1024px PNG. Tell the user the exact path and open it in the native OS viewer (macOS: open "<path>"). To ship a macOS app, drop it into a .iconset directory and run iconutil -c icns <name>.iconset. For an iOS App Store upload, flatten onto an opaque background first (Apple rejects icons that contain an alpha channel).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYes
thinking_levelNohigh
enable_image_searchNo
enable_google_searchNo
reference_image_pathsNo
allow_icon_words_in_promptNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description must carry the full burden. It thoroughly explains forced behaviors: transparent background, square aspect ratio, 1K resolution, PNG format, and cut-out only. It also describes the prompt guard and its exception. However, it lacks mention of authentication, rate limits, or side effects beyond file creation. For a generation tool, the disclosed traits are comprehensive, earning a 4.

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?

The description is well-structured with sections, emojis, and clear formatting. It front-loads the purpose and forced settings. However, it is quite verbose and could be trimmed; some information is repeated (e.g., the prompt rule is emphasized multiple times). Still, the organization aids readability and earns a 4.

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, 1 required, output schema exists), the description covers all aspects: purpose, usage guidelines, prompt rules, parameter details, result format, and next steps (open in viewer, convert to .icns, etc.). It leaves little ambiguity, making it highly complete.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must fully explain parameters. It does so with a dedicated '📋 PARAMETERS' section that details each parameter's purpose, constraints, and defaults (e.g., prompt must avoid icon-related words, reference_image_paths up to 14, thinking_level options). This adds significant meaning beyond the bare 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 clearly states the tool's purpose: generating app icons and logos. It explicitly distinguishes from the sibling tool generate_image by saying 'Use THIS tool — not generate_image — whenever the user asks for an app icon, application icon, .icns, etc.' This provides a specific verb+resource and sets it apart from alternatives.

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?

The description gives explicit guidance on when to use this tool vs generate_image, including a list of use cases. It also provides clear rules for writing prompts (what to include and avoid), and explains when to use the escape hatch for allow_icon_words_in_prompt. This covers both when to use and when not to.

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/nikships/ultimate-image-gen-mcp'

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