ytm-runlist-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YTM_RUNLIST_DATA_DIR | Yes | Absolute path to the data directory where runlist files are stored (e.g., .runlist). | |
| GOOGLE_CLIENT_SECRETS_FILE | Yes | Absolute path to the Google OAuth client secrets JSON file. | |
| YTM_RUNLIST_GOOGLE_TOKEN_FILE | Yes | Absolute path to the Google OAuth token JSON file. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthA | Return MCP server version and local OAuth status. |
| get_running_strategy_options_toolB | Return objective running pace strategy options for the LLM to present to the user. |
| list_youtube_music_playlistsA | List playlists owned by the authenticated user's YouTube account. |
| get_playlist_tracks_toolB | Return tracks from a playlist, including playlist_item_id needed for reordering. |
| validate_reorder_planA | Validate a proposed full in-place reorder and return the minimal update actions. ordered_playlist_item_ids must contain every existing playlist item exactly once. running_plan is optional metadata from the LLM and is validated only for shape. |
| reorder_original_playlistA | Reorder the original playlist in place. dry_run defaults to true. Set dry_run=false and confirm_modify_original=true only after the user explicitly confirms modifying the original playlist. |
| create_reordered_playlist_copy_toolA | Create a new playlist copy from a proposed order. Unlike in-place reorder, ordered_playlist_item_ids may be a subset of the source playlist. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| running_playlist_editor_workflow | Workflow instructions for LLMs using this MCP server. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a distinct purpose: creating a copy, fetching tracks, providing running strategy options, health check, listing playlists, reordering in-place, and validating a reorder plan. No two tools overlap in functionality.
Tool names are inconsistent: some end with '_tool', some don't ('health' is a single word), and verb phrases vary ('list_youtube_music_playlists' vs 'reorder_original_playlist'). No uniform pattern.
With 7 tools, the server is well-scoped for its domain of YouTube Music playlist reordering and running strategy integration. Each tool feels necessary and the count is within the ideal range.
The tool set covers key operations: list playlists, get tracks, get running strategy options, validate a plan, reorder a playlist, and create a copy. No obvious gaps for the runlist management purpose.