Skip to main content
Glama
Sign In
Spotify MCP Server

Spotify MCP Server

by walter-kai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

spotify_get_saved_albums

Retrieve albums saved in the current Spotify user's library, with limit and offset controls to page through results.

Instructions

Get albums saved in the current user's library

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spotify_get_saved_albums"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of albums to return (default: 20)
offsetNoIndex of first album to return (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only retrieval via 'Get' but discloses no behavioral traits such as authentication requirements, pagination behavior, rate limits, or response format.

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?

A single, front-loaded sentence that states the purpose without filler. Every word earns its place.

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

Completeness3/5

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

For a simple getter with zero required parameters and a fully documented schema, the description is adequate but not complete. It omits any mention of return format (no output schema exists) and behavioral context like auth requirements, leaving the agent with only the basic purpose.

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 the schema already documents both limit and offset parameters. The description adds no parameter-level information, so the baseline of 3 is appropriate.

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 states a specific verb ('Get') and resource ('albums saved in the current user's library'), which distinguishes it from sibling spotify_get_saved_tracks. However, it provides no explicit sibling differentiation or scope boundaries beyond the noun, so it falls short of a 5.

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

Usage Guidelines2/5

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

No when-to-use guidance, no alternatives named, and no prerequisites. The description only states what the tool does, not when to choose it over other saved-item tools.

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