Skip to main content
Glama
Sign In
lyricmood-mcp

lyricmood-mcp

by yigitates17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get My Top Tracks

get_my_top_tracks

Retrieve your most-played Spotify tracks for a chosen period, ranked from most played, to explore your listening habits and understand why you like what you like.

Instructions

The user's most-played Spotify tracks over a time range, most played first. Good starting point for "why do I like what I like?".

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tracks (1-50).
time_rangeNoshort_term ≈ last 4 weeks, medium_term ≈ 6 months, long_term ≈ 1 year.medium_term

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?

Although there are no annotations, the description provides helpful behavioral context by noting that results are returned 'most played first.' This transparency helps the agent understand the hierarchy of the results.

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?

The description is highly concise and efficient, delivering the core utility of the tool in two clear, relevant sentences without any unnecessary padding.

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?

With 100% schema coverage, the definition is highly complete. The description successfully adds the 'most played first' ordering behavior, which is vital context missing from the schema.

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?

Given that the schema coverage is 100%, the schema description already provides all necessary meaning for both parameters (limit and time_range). The description does not add unique semantic meaning beyond restating the context.

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 clearly states the tool's function: retrieving a user's most-played tracks over a time range. It is distinct from sibling tools like get_saved_tracks by focusing on usage statistics rather than ownership.

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?

The description offers very little guidance on when to use this tool versus others. While the phrase 'Good starting point' provides a use case, it does not suggest scenarios where this tool is superior to alternatives like getting recently played tracks or saved tracks.

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