Skip to main content
Glama

ampache_playlists

Destructive

Manage Ampache playlists and smartlists: list, view songs, create, edit, add or remove tracks, generate, hash, and delete—writes run only when confirmed.

Instructions

Playlists and smartlists: list, get, songs, create, edit, add, remove, generate, hash, and delete. Writes run only when confirm is true and AMPACHE_ALLOW_WRITES=true. List actions default to offset 0 and limit 25 (max 500). Actions: playlist, playlist_add, playlist_create, playlist_delete, playlist_edit, playlist_generate, playlist_hash, playlist_remove, playlist_remove_song, playlist_songs, playlists, smartlist, smartlist_delete, smartlist_songs, smartlists, user_playlists, user_smartlists.

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": "ampache_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
addNo
condNo
flagNo
modeNo
nameNo
songNo
sortNo
typeNo
albumNo
checkNo
clearNo
exactNo
itemsNo
limitNo
ownerNo
trackNo
actionYesAmpache operation to call.
artistNo
filterNo
formatNo
offsetNo
tracksNo
updateNo
confirmNoBoolean true runs the write when AMPACHE_ALLOW_WRITES is true. Omit it or pass false for a dry-run preview that sends nothing. The string true is rejected.
includeNo
show_dupesNo
hide_searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and non-idempotent, so the agent knows reads and writes are mixed. The description adds context beyond that: the two-factor write gate (confirm plus AMPACHE_ALLOW_WRITES) and the effective dry-run when omitted, which meaningfully de-risks a destructive tool. It stops short of saying what delete/remove actually destroys or which actions count as writes versus reads.

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?

Structure is good: capability summary first, then the write-gating constraint, then pagination defaults, then the action vocabulary. The trailing action enumeration largely restates the schema's action enum and eats space, but it is a single compact sentence and nothing else is padded.

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

Completeness2/5

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

This is a 28-parameter, 17-action polymorphic tool with destructive writes and no output schema, so the description must carry a lot — and it doesn't. An agent cannot tell from this text which parameters belong to playlist_generate versus playlist_edit versus smartlist, nor what any action returns, making incorrect invocations likely despite the good write-gate note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 7% across 28 parameters, so the description carries most of the burden — yet it only explains confirm, offset, and limit. The other ~25 parameters (id, add, cond, mode, sort, items, owner, tracks, update, include, show_dupes, hide_search, flag, check, clear, exact, etc.) are given no meaning in either the schema or the description, leaving the agent to guess which parameters each of the 17 actions requires.

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 description names a specific resource (playlists and smartlists) and enumerates the operations (list, get, songs, create, edit, add, remove, generate, hash, delete) before listing the 17 action values, so an agent knows this is the playlist-domain tool. It does not explicitly distinguish itself from the sibling catalog/library/podcast tools, but those cover unrelated resources, so the domain separation is implicit.

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?

It gives a clear hard precondition for writes — 'Writes run only when confirm is true and AMPACHE_ALLOW_WRITES=true' — and states that list actions default to offset 0 and limit 25 (max 500), which is genuine usage context. However, there is no guidance on which action to choose when (e.g., playlists vs user_playlists vs smartlists, or playlist_add vs playlist_create); the action list is a bare enumeration with no selection criteria.

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