Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

statsfm_top_artists

Retrieve a stats.fm user's most-streamed artists by user ID. Set the ranking window, limit, and offset to get the desired slice of listening history.

Instructions

A stats.fm user's most-streamed artists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo1–100. Default: 10
rangeNoRanking window. Default: lifetime
offsetNoStart position (0-based). Default: 0
user_idYesstats.fm user id or customId (e.g. "martijn")
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.29.0

TDQS

C2.9/5.0
Behavior2/5

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

Since annotations are absent, the description should clarify whether the operation is read-only and any side effects or access requirements. It only states a data fact, leaving behavioral aspects unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short phrase with no filler, which is concise. However, it could be improved by adding a verb like 'Get' for better structure.

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

Completeness2/5

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

The description does not explain the return structure, the meaning of response_format, or the difference between limit and max_results, which are essential given the six-parameter schema. This leaves the description incomplete.

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?

All six parameters have descriptions in the schema, covering range, limit, offset, etc. The tool description adds no additional semantic information, so it meets the baseline for schema coverage.

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 identifies the resource (a stats.fm user) and the data returned (most-streamed artists), but it is phrased as a noun phrase rather than an explicit action, which slightly reduces clarity.

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 does not mention alternative tools or provide any condition for when to use this tool over siblings like statsfm_top_tracks, so an agent receives no guidance on tool selection.

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