com.losercoreplaylist/creative-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_playlistA | Search four starter tracks by song, artist or mood. This is a dated starter selection, not a live or complete Spotify catalogue. Returns metadata and listening links only. |
| get_creation_templateA | Return one of two original adult-character scene prompts for a PS2-inspired concept. This prepares text only and never submits or charges an AI generation request. |
| prepare_video_projectA | Prepare a free local-workspace JSON draft from 1–12 song/artist title cards and three original captions. Save the project field as JSON, then import it on the linked workspace. It does not render a video, fetch audio or provide song lyrics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_playlist_video | Draft an original caption and timing brief for the local workspace. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| playlist-starter-selection | Four starter tracks and their scope; no audio or song lyrics. |
| creative-workspace-guide |
TDQS
Scored across 3 tools
Each tool maps to a distinct step: searching the starter track list, fetching a scene-prompt template, and assembling a JSON project draft. There is mild thematic overlap between search_playlist and prepare_video_project since both concern songs, but the descriptions make clear that one returns metadata and the other builds a file draft.
All three tools follow a consistent snake_case verb_noun convention (search_playlist, get_creation_template, prepare_video_project). Verb choices accurately reflect each action's read-versus-prepare semantics.
Three tools is minimal but matches a narrowly scoped creative-asset helper with a clear three-step pipeline. It is not thin in the problematic sense, since each tool covers a genuinely different stage of the workflow.
The surface is read-and-prepare only: there is no way to retrieve, list, or revise a previously prepared project draft, and no tool exposes the linked workspace or template list. Rendering, audio fetching, and lyric lookup are explicitly out of scope, so the remaining gaps are structural rather than broken.