Skip to main content
Glama

streamdeck_write_page

Create or update a Stream Deck page manifest with buttons, icons, and dial layouts. Avoids manifest overwrite by the Elgato app by requiring explicit auto-quit consent.

Instructions

Create a new page or replace/update an existing Stream Deck desktop page manifest. IMPORTANT: the Elgato desktop app overwrites profile manifests from its in-memory state on quit, so writes made while the app is running are lost. This tool refuses to write when the app is running unless auto_quit_app=True is passed. Call streamdeck_restart_app once your edits are complete to make the changes visible on the device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_nameNo
profile_idNo
page_indexNoZero-based page index. Accepts int or string form.
directory_idNo
page_nameNoOptional page name stored in the page manifest.
buttonsNoButtons to write. Use streamdeck_create_action to build Open or script-backed actions. Accepts a JSON array or a JSON-encoded string — some MCP clients stringify nested arrays in transit.
clear_existingNoIf true, replace the page contents with the provided buttons. Defaults to true. Accepts bool or string form.
create_newNoCreate a new page instead of updating an existing one.
make_currentNoWhen true, make the page the active current page after writing.
auto_quit_appNoIf true and the Elgato Stream Deck desktop app is running, quit it (graceful AppleScript first, then killall) before writing. Required when the app is running or the write will raise an error. Defaults to false so callers must explicitly consent to quitting it.
Behavior5/5

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

With no annotations provided, the description carries the full burden and excels. It discloses key behaviors: the app's in-memory state overwriting on quit, the tool's refusal to write when the app is running without auto_quit_app=True, and the need to restart the app to make changes visible. This provides high transparency for a mutation tool.

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 a single paragraph of three sentences. It is front-loaded with the purpose, then delivers critical warnings and a procedural tip. Every sentence is informative with no redundancy or fluff.

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's complexity (10 params, no annotations, no output schema), the description covers the main purpose, behavioral warnings, and a cross-reference to sibling tools (streamdeck_create_action, streamdeck_restart_app). It does not explain return values (no output schema needed) and slightly lacks explicit sibling comparisons, but overall it equips an agent well.

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 description coverage is 70%; the description adds value beyond the schema. It explains that streamdeck_create_action can build actions for the buttons parameter, notes that some MCP clients stringify nested arrays, and clarifies auto_quit_app's default false. The summary description does not detail every parameter but the added context compensates for the remaining 30% gap.

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 creates a new page or replaces/updates an existing Stream Deck desktop page manifest. It uses specific verbs ('Create', 'replace/update') and identifies the resource ('Stream Deck desktop page manifest'). This distinguishes it from sibling tools like streamdeck_read_page (read-only) and streamdeck_restart_app (restart).

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 provides critical usage guidance: it warns that the Elgato app overwrites manifests on quit, explains that writes are refused unless auto_quit_app=True when the app is running, and recommends calling streamdeck_restart_app after edits. It implies when to use this tool versus reading or restarting, though it does not explicitly list alternatives or when not to use it.

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/verygoodplugins/streamdeck-mcp'

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