Skip to main content
Glama
ethbak

Icon Composer MCP

by ethbak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

export_marketing

Exports a flat, opaque 1024x1024 PNG for App Store Connect marketing assets. Removes Liquid Glass effects and alpha channel for direct upload.

Instructions

Export a flat marketing PNG for App Store Connect. No Liquid Glass effects, no alpha channel. Produces a 1024x1024 (default) opaque PNG ready for upload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoOutput size in pixels (default 1024)
bundle_pathYesPath to .icon bundle
output_pathYesOutput path for the PNG file
return_imageNoReturn the rendered image inline as base64 (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / return_image
      Added value: +{
+  "default": true,
+  "description": "Return the rendered image inline as base64 (default true)",
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses key behaviors (no effects, no alpha, opaque, default size) but omits details about the return_image parameter behavior and output_path expectations. The description is adequate but not fully transparent about all parameter-driven behaviors.

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?

Two sentences, no redundancy, front-loaded with the core action. Every word adds value. Excellent conciseness.

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

Completeness3/5

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

Given 4 parameters, no output schema, and no annotations, the description covers the main purpose and constraints but does not explain the return_image parameter or output_path format. It is sufficient for a straightforward export tool but could be more complete.

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 description coverage is 100%, so baseline is 3. The description adds minimal extra parameter meaning beyond the schema (mentions default 1024x1024 size, which is already in schema). It does not elaborate on return_image or output_path beyond what the schema provides.

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 exports a flat marketing PNG for App Store Connect, specifying no Liquid Glass effects, no alpha channel, and default 1024x1024 size. It distinguishes from siblings like render_liquid_glass and export_preview by focusing on the flat, opaque export use case.

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 explicitly says 'No Liquid Glass effects, no alpha channel', which tells the agent not to use this tool when effects are needed. It implies the tool is for final marketing export, but lacks explicit when-to-use vs alternatives like export_preview. Still provides good contextual guidance.

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