Skip to main content
Glama
lastfm-taste-mcp

lastfm-taste-mcp

by nurasik14

user_get_top_albums

Read-only

Retrieve a user's most played albums over a chosen time window, including play counts, to analyze listening habits and identify top albums.

Instructions

The user's most played albums in a time window, with play counts.

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

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, for going past the first `limit` items
userNoLast.fm username. Leave empty for the configured user (LASTFM_USERNAME).
limitNoHow many results to return
periodNoTime window: 7day, 1month, 3month, 6month, 12month or overall7day

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds that results include play counts, which is modest but real information about the payload; it says nothing about ranking order, ties, or empty-user fallback behavior.

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 tightly written sentence that front-loads the resource and scope with no filler. Nothing could be cut without losing information.

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 four-parameter read-only lookup with full schema coverage and no output schema, the description covers the resource, scope, and one return-value trait (play counts), which is enough to call it correctly. It stops short of describing result ordering or the empty-user fallback, but those are minor omissions at this complexity.

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 page, user, limit, and period are all fully documented in the schema itself. The description adds no meaning beyond 'time window' gesturing at period, which is the baseline expectation when the schema does the heavy lifting.

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 names a specific resource (albums), a scope (a given user's most played), and a dimension of the result (play counts, time window). An agent can distinguish it from user_get_top_tracks or user_get_top_artists by resource, but it never explicitly contrasts itself with user_get_weekly_album_chart or album_get_top_tags, which overlaps conceptually.

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?

There is no when-to-use or when-not-to-use guidance. The phrase 'in a time window' loosely implies the period parameter drives scope, but nothing tells the agent why to pick this over user_get_weekly_album_chart or how it differs from the weekly charts siblings.

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