Skip to main content
Glama
Sign In
lyricmood-mcp

lyricmood-mcp

by yigitates17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Saved Tracks

get_saved_tracks

Retrieves a user's Spotify Liked Songs, most recently liked first, and supports limit/offset paging so you can browse saved tracks.

Instructions

The user's Liked Songs on Spotify, most recently liked first. total is the full count; page with offset.

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": "get_saved_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tracks (1-50).
offsetNoSkip this many (for paging).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose ordering (most recently liked first) and that `total` is the full unpaged count, which is genuinely useful. It omits auth requirements (this is per-user data) and any statement about what a page response contains beyond the count.

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?

Two short sentences, front-loaded with the resource and ordering, followed by the paging note. Nothing is redundant or 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?

For a simple two-parameter read tool with no output schema, the description covers resource identity, sort order, and pagination strategy, plus the meaning of `total`. Only the per-user authentication requirement and result item shape are left unstated, which are minor for a tool this simple.

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 coverage is 100%, so both `limit` and `offset` are already documented, making 3 the baseline. The description reinforces `offset` as the paging control and explains that `total` reflects the unpaged count, but adds no format or edge-case detail beyond the schema.

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?

States a specific verb and resource: the user's Liked Songs on Spotify, with an explicit ordering (most recently liked first). An agent can distinguish it from get_playlist_tracks and get_my_top_tracks by the 'Liked Songs' framing, though no sibling is named outright.

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

Usage Guidelines3/5

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

The description gives paging guidance ('page with `offset`') but never says when to prefer this over get_my_top_tracks, get_playlist_tracks, or search_track. Usage is implied by the resource name rather than stated as a selection rule.

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