Skip to main content
Glama

Change playlists

AccountPlaylistsWriteTool
Destructive

Change device playlists: add, reorder, copy, update, duplicate or delete items, replace an item's schedule, and create or change mashups. deletePlaylistItem is destructive.

  • addDevicePlaylistItem: Add a plugin instance to a device playlist — params: device_id (path), plugin_setting_id (body: Plugin setting id)

  • reorderDevicePlaylist: Reorder a device playlist — params: device_id (path), playlist_item_ids (body)

  • bulkUpdateDevicePlaylist: Show or hide several playlist items on a device at once — params: device_id (path), action_type (body: one of hide, show), playlist_item_ids (body)

  • copyDevicePlaylist: Copy a playlist to another device — params: device_id (path), target_device_id (body: Destination device id)

  • updatePlaylistItem: Update a playlist item — params: id (path), visible (body), palette_id (body), font_family (body), text_scale (body: one of small, regular, large, xlarge, ), theme (body)

  • deletePlaylistItem: Remove a playlist item — params: id (path)

  • replacePlaylistItemSchedule: Replace when a playlist item is allowed to display — params: item_id (path), week_schedules (body: each {week_days: 0 is Sunday through 6 is Saturday, start_time: HH:MM, 00:00 to 23:59, end_time: HH:MM, 00:00 to 23:59}), date_range (body: Only display between these dates. Null when no dates are set)

  • duplicatePlaylistItem: Duplicate a playlist item — params: id (path)

  • createDeviceMashup: Add a mashup to a device playlist — params: device_id (path), layout (body: one of 1x1, 1Tx1B, 1Lx1R, 1Tx2B, 2Tx1B, 1Lx2R, 2Lx1R, 2x2, 3x3), grid_config (body: each {pos, col, row, cs, rs}), contents (body: Plugin setting id by position; a position left out renders empty)

  • updateMashup: Change the sections of a mashup — params: id (path), contents (body: Plugin setting id by position), health_notification_enabled (body)

  • resetMashupHealth: Reset a mashup past its health breaker — params: id (path)

Input Schema

NameRequiredDescriptionDefault
actionYesThe API operation to run
paramsNoThe operation's path, query and body parameters by name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description usefully refines this by localizing destruction to deletePlaylistItem rather than implying every action is destructive. It still omits auth requirements, reversibility, and per-action idempotency behavior, which matters given idempotentHint=false.

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 summary sentence is front-loaded and the per-action bullets are tightly scoped to routing and parameters, each earning its place. It is long, but the length is justified by 11 distinct actions with no wasted prose.

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 write dispatcher with no output schema, the description covers every action and its parameters completely enough to invoke correctly. It could add return-value expectations and permission requirements, but nothing essential for invocation is missing.

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?

The schema only exposes a generic {action, params} wrapper, so the description carries nearly all parameter meaning. It documents each action's path/body params, enumerates value sets (layout 1x1..3x3, action_type hide/show), and specifies formats (week_days 0=Sunday, HH:MM 00:00-23:59, contents by position) — far beyond the 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?

Opens with a specific verb+resource ('Change device playlists') and enumerates the full action scope (add, reorder, copy, update, duplicate, delete, schedules, mashups). Combined with the sibling AccountPlaylistsReadTool name, an agent can immediately distinguish this write dispatcher from the read tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The bulleted action list gives context for selecting the correct sub-action, which is useful routing guidance. However, it never states when to use this tool versus AccountPlaylistsReadTool, nor any exclusions or prerequisites; usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources