Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

save_items

Save tracks, albums, shows, episodes, or audiobooks to your Spotify library by submitting URIs. Supports up to 50 items per request, with dry-run preview to validate before changing anything.

Instructions

Legacy per-type variant (kept for grandfathered app credentials that lack unified /me/library access). Prefer save_to_library. Save one or more items to the user's library. Accepts track, album, show, episode, and audiobook URIs (e.g. spotify:track:abc). Max 50. Set dry_run=true to preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urisYesSpotify URIs to save (e.g. ["spotify:track:abc", "spotify:album:xyz"])
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only: validate inputs and describe exactly what would change without performing it",
+  "type": "boolean"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.1

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are present, so the description carries the behavioral burden. It discloses the legacy status, the credential limitation, the maximum of 50 items, and the dry_run preview behavior. It does not discuss idempotency or failure behavior, but for a straightforward save operation it provides meaningful non-obvious context.

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 description is compact and every sentence carries either routing, context, or parameter guidance. It is slightly telegraphic ('Max 50', 'per-type variant') but not padded. Minor jargon like 'grandfathered app credentials' is acceptable because the next sentence explains its relevance.

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

Completeness5/5

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

For a 3-parameter tool with no output schema, this is complete: it explains when to use it, why it exists, what it saves, which URI types are valid, the size limit, and how to preview. The response_format parameter is already documented in the schema, so its absence from the description is not a gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by enumerating accepted URI types (track, album, show, episode, audiobook), giving a concrete URI example, and clarifying that dry_run previews the change. These specifics go beyond the schema's generic 'Spotify URIs' phrasing.

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?

The description states a specific verb ('Save') and resource ('user's library'), enumerates supported URI types, and explicitly labels itself as a legacy per-type variant. It also names the preferred sibling (save_to_library), so an agent can distinguish it immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly instructs 'Prefer save_to_library' and gives the exact condition for choosing this tool: grandfathered app credentials that lack unified /me/library access. This is clear when-to-use and when-not-to-use guidance, not just implied context.

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