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), text_scales (body: Text scale by position; a position left out follows the device)

  • updateMashup: Change the sections of a mashup — params: id (path), contents (body: Plugin setting id by position), text_scales (body: Text scale by position, for the positions in contents. Blank goes back to the device scale), health_notification_enabled (body), stopped_notification_enabled (body: Email the owner when the mashup stops refreshing)

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "AccountPlaylistsWriteTool"
  }
}

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 readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the safety profile is known; the description adds value by pinpointing which sub-operation is destructive rather than leaving the whole tool uniformly dangerous. It also discloses non-obvious semantics such as null date_range meaning no date restriction, omitted mashup positions rendering empty, and blank text scales reverting to device scale. It does not cover auth/permission requirements or what a failure looks like, so not a 5.

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 one-line purpose statement is front-loaded, followed by a scannable per-action bullet list where each line maps to one enum value and earns its place. Some duplication with the action enum is unavoidable but the param annotations per bullet are genuinely additive. Density is high but appropriate for an 11-action polymorphic tool.

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 polymorphic dispatch tool with no output schema and a free-form params object, the description covers every action's inputs and key behavioral quirks, which is the main completeness risk. Gaps remain around return values, error behavior, and permissions for a destructive multi-operation tool, keeping it below a 5.

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 'params' object, so the description carries the real burden and does it well: it names each action's path vs body parameters, lists enums (hide/show, small/regular/large/xlarge, layout grids like 1Tx2B), and specifies formats such as week_days 0=Sunday through 6 and HH:MM ranges. This is meaning well beyond what the input schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource ('Change device playlists') and enumerates the concrete operations: add, reorder, copy, update, duplicate, delete, replace schedule, and mashup create/change. An agent can tell this is the mutation counterpart to the read tool by name and verb alone. It stops short of explicitly naming AccountPlaylistsReadTool as the read-only alternative, which keeps it from a 5.

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?

Each of the 11 actions is paired with a one-line statement of what it does, so an agent can pick the right action from the enum without guessing. It also flags that deletePlaylistItem is destructive, which is a useful routing signal. There is no explicit 'when not to use' guidance, no prerequisites, and no note on when to prefer the read tool.

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