Skip to main content
Glama

streamdeck_create_icon

Generate PNG icons for Stream Deck buttons and touchstrips using Material Design Icons or text. Supports batch creation of multiple icons in one call.

Instructions

Generate one or many PNG icons. Button icons are 72x72 px; touchstrip segment icons are 200x100 px (use shape='touchstrip'). For a single icon: pass 'icon' (a Material Design Icons name like 'mdi:cpu-64-bit') OR 'text' (mutually exclusive with 'icon' — titles go on streamdeck_write_page's 'title' field since Elgato overlays them on images). For a full deck (often 30+ icons): pass 'icons' as a list of spec dicts to generate them all in one call and avoid the round-trip timeouts serial calls hit. ~7400 MDI icons bundled offline; unknown names return close-match suggestions. Returns either a single {path, size, ...} dict or {"icons": [...]} when 'icons' is used (each list element is a per-icon result or an {"error"} entry for that spec).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconNoMaterial Design Icons name, e.g. 'mdi:cpu-64-bit', 'mdi:volume-high', 'mdi:microphone'. The 'mdi:' prefix is optional. Aliases are honored.
textNoText for a centered text-only icon. Mutually exclusive with 'icon'. For icon buttons that need a label, use the button's 'title' field on streamdeck_write_page.
iconsNoBatch generation: a list of icon spec objects, each carrying the same fields as a single-icon call (icon/text/icon_color/bg_color/icon_scale/shape/transparent_bg/text_color/font_size/filename). When this field is present, all other single-icon fields at the top level are ignored and the response shape becomes {"icons": [per-spec result]}. Use this for 30+ icon decks to avoid per-call round-trip cost. Accepts either a JSON array or a JSON-encoded string containing an array — some MCP clients stringify nested arrays in transit.
shapeNoOutput canvas. 'button' (default) is 72x72 — keypad keys and encoder dial faces. 'touchstrip' is 200x100 — per-segment background above a Stream Deck + / + XL dial; pair with a button's strip_background_path on streamdeck_write_page.
bg_colorNo
filenameNo
font_sizeNo
icon_colorNoHex color for the icon glyph, e.g. '#00ff88'. Defaults to text_color.
icon_scaleNoFraction of the canvas the glyph bounding box fills (0.1-1.0). Defaults to 1.0 — edge-to-edge, matching how Elgato's own icons fill the touchstrip slot. Reduce to ~0.75-0.85 for keypad buttons that also have a bottom title so the glyph doesn't touch the label.
text_colorNo
transparent_bgNoGenerate an RGBA PNG with a transparent canvas instead of filling with bg_color. Use this for dial Icons that overlay a touchstrip background so the glyph composes naturally. Leave false (default) for keypad faces and touchstrip backgrounds.
Behavior5/5

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

No annotations provided, so the description carries full burden. It discloses return shapes (single dict or array), behavior for unknown MDI names (close-match suggestions), that batch 'icons' ignores other top-level fields, and that some MCP clients stringify nested arrays. This level of detail is comprehensive.

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?

Description is well-structured with a clear summary first, then breakdown of single vs batch, then additional details. Though slightly lengthy, every sentence provides useful context. Front-loaded with the most critical information.

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 tool with 11 parameters and no output schema, the description covers the main use cases, return types, batch vs single distinction, and error handling. It adequately informs an agent about how to use the tool effectively, though could mention potential limitations or dependencies more explicitly.

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?

With 64% schema description coverage, the description adds significant meaning beyond the schema: explains that 'mdi:' prefix is optional and aliases honored, provides example MDI names, clarifies 'text' mutual exclusivity, recommends icon_scale for different setups, and describes transparent_bg usage. This adds value beyond the raw 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?

Description clearly states 'Generate one or many PNG icons' with a specific verb and resource. It distinguishes from sibling tools by specifying icon creation, not actions or page writing, and provides context on icon sizes and shapes.

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?

Description explains when to use single icon vs batch mode, mentions mutual exclusivity of 'icon' and 'text', and advises using batch for many icons to avoid timeouts. It also clarifies that titles belong on streamdeck_write_page, guiding correct usage. Lacks explicit when-not-to-use but the guidance 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/jack-arturo/streamdeck-mcp'

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