Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

save_to_library

Save up to 40 Spotify items (tracks, albums, episodes, shows, audiobooks, users, playlists) to a user's library. Preview by default; set dry_run=false to commit.

Instructions

Preferred. Accepts the widest URI mix (track, album, episode, show, audiobook, user, playlist) in one request. Save one or more items to the user's library via Spotify's unified library endpoint. Max 40. PREVIEWS BY DEFAULT — pass dry_run=false to commit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urisYesSpotify URIs to save (e.g. ["spotify:track:abc", "spotify:user:xyz"])
dry_runNoPreview only: perform the read side and return a PLAN without changing anything. Default true — pass dry_run=false to commit.
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.1
    • addedInput schema / properties / dry_run / default
      Added value: +true
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only: validate inputs and describe exactly what would change without performing it"New value: +"Preview only: perform the read side and return a PLAN without changing anything. Default true — pass dry_run=false to commit."
  2. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv1.26.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only supply destructiveHint=false, so the description carries the real behavioral load. It discloses the critical dry-run/preview default ('PREVIEWS BY DEFAULT — pass dry_run=false to commit'), which an agent would otherwise get wrong, plus the hard 40-item cap — genuine value beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short clauses, front-loaded with the differentiator ('Preferred') and the commit behavior. Every sentence contributes and nothing is padded.

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?

With no output schema, the description does note that a preview returns a PLAN and that response_format controls output shape, which covers the main return-value concern. It stops short of describing error behavior or partial-failure handling, a minor gap for a batch mutation tool.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters are already documented in the schema, including the dry_run preview semantics and the maxItems cap. The description restates the 40 limit and preview behavior but adds no syntax, format, or edge-case detail beyond what the schema provides.

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?

States a specific verb and resource ('Save one or more items to the user's library'), names the underlying endpoint, and explicitly enumerates the accepted URI types. The 'Preferred' framing plus the URI-mix claim clearly distinguishes it from siblings such as remove_from_library and add_to_playlist.

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?

Signals this is the preferred path for library saves and that it consolidates mixed URI types in one request, which routes the agent here over narrower alternatives. However, it never names the alternatives it is preferred over (e.g. add_to_playlist) or states when-not to use it, so the guidance is strong but not fully explicit.

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

Deploy Server

Other Tools