Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

tag_management

Manage local genre tags for artists, adding or removing tags to control library genre reports and filtering. Supports dry-run preview of changes.

Instructions

Declare or retract genre tags for an artist in your local sidecar (~/.spotify-mcp/genre-tags.json), which library_genre_report and filter_by_genre consume. add requires at least one tag; remove drops the listed tags, or the artist entirely when none are listed. Supports dry_run preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags to add/remove; omit on remove to drop the artist entirely
actionYesadd tags to an artist, or remove tags/artist
artistYesArtist name exactly as it appears in your library
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv1.26.1

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the minimal destructiveHint annotation, the description discloses the exact sidecar file path, the persistence model, the consuming tools, the add/remove semantics, and the dry_run preview capability. It does not discuss irreversibility or edge cases like missing files, but it adds meaningful behavioral context.

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 wasted words. The primary purpose and file location are front-loaded, followed by compact action semantics and dry-run mention. Every clause earns its place.

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?

Given the lack of an output schema and minimal annotations, the description covers the essential context: what the tool does, where state lives, what consumes it, and how add/remove/dry_run behave. It omits details like whether the sidecar file is auto-created or whether tags are case-sensitive, but these are not critical for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds at least one meaningful constraint not visible in the schema: 'add requires at least one tag.' It also reinforces the distinction between removing listed tags and removing the artist entirely, adding context beyond bare parameter names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: declare or retract genre tags for an artist in a local sidecar file. It also names the consuming tools (library_genre_report and filter_by_genre), which distinguishes it from the many sibling tools.

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?

The description gives clear context by explaining that the tags feed library_genre_report and filter_by_genre, implying when an agent should use this tool. It also provides operational guidance (add requires at least one tag; remove can drop an artist entirely), though it does not explicitly contrast with alternatives.

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