Skip to main content
Glama
Sign In
lastfm-taste-mcp

lastfm-taste-mcp

by nurasik14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

user_get_recent_tracks

Read-only

Retrieve individual Last.fm plays with timestamps, newest first and optionally filtered by a date range, to review listening history or count plays.

Instructions

Individual plays with timestamps, newest first, optionally within a date range. Use for "what did I listen to on Tuesday", listening times, or counting plays yourself.

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_recent_tracks"
  }
}

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
sinceNoOnly plays after this local date/time, ISO format, e.g. 2026-10-23 or 2026-10-23T18:00
untilNoOnly plays before this local date/time, ISO format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe read. The description adds genuinely useful behavior beyond that: results are per-play events with timestamps and ordered newest first. It does not mention pagination depth, how far back history goes, or how results are bounded, so the added context is real but limited.

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 sentences with no filler; the ordering and granularity guarantee is front-loaded before the use-case examples. Every clause carries information an agent can act on.

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 read-only, zero-required-parameter listing tool with full schema coverage and no output schema, the description covers what the results are (individual plays with timestamps) and their ordering. It leaves return-field shape and pagination boundaries unstated, but that is a minor gap given how self-describing the schema is.

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 page, limit, user, since, and until are all documented in the schema itself. The description only echoes the optional date-range capability that since/until already explain, adding no format or interaction detail beyond the schema. Baseline 3 applies.

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 gives a specific verb+resource: it returns individual play events with timestamps, newest first, with an optional date range. That distinguishes it implicitly from the aggregated siblings (user_get_top_tracks, user_get_weekly_track_chart) by emphasizing per-play granularity, though it never names a sibling outright.

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?

It states concrete usage contexts ("what did I listen to on Tuesday", listening times, counting plays yourself), which is clear when-to-use guidance. The phrase "counting plays yourself" hints that aggregation is the caller's job rather than a sibling's, but no alternative tool is named and no when-not-to-use condition is given.

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