Skip to main content
Glama
bestimmaa
by bestimmaa

Search Roon music

search_music

Search for artists, albums, tracks, playlists, radio stations, or genres in your Roon library. Returns candidates ready for playback via get_tracks_for.

Instructions

Use this when the user names music to find — an artist, album, track, playlist, radio station, or genre (e.g. "find Tycho", "look up the album In Rainbows", "play some Psytrance", "anything by Ryuichi Sakamoto?"). Resolves a free-text query into ranked Roon browse candidates. Optionally restrict to one item type (artist, album, track, genre, playlist, radio); for non-genre types, an empty typed search broadens to all categories. type:"genre" is special — genres don't appear in Roon's flat search, so the server walks the dedicated Genres tree and returns the nearest-match genre nodes (with parent path in the subtitle) without broadening; e.g. "Psychedelic Trance" yields "Psytrance"/"Trance". Set includeStreaming:true (only meaningful for type:"genre") to also pull a track mix from streaming services (e.g. TIDAL): the server takes the genre-relevant albums and samples tracks across them, so library genre nodes come first and ready-to-play streaming tracks are appended after. Returns opaque, session-scoped item keys for use by the playback tools — pair with get_tracks_for to expand, then play_now or enqueue_and_play.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWhat to search for — an artist, album, track, playlist, radio, or genre name (e.g. 'Tycho', 'In Rainbows', 'Dark Ambient').
typeNoRestrict the search to one item type. Omit to broaden across all non-genre categories. Use 'genre' for music-genre lookups.
limitNoMax candidates to return (default 10).
includeStreamingNoOnly for type 'genre': also pull a track mix from streaming services (e.g. TIDAL). Library genre nodes come first, then sampled streaming tracks. Default false (library only).
Behavior5/5

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

No annotations exist, so description fully covers behavior: explains free-text resolution, optional type restriction, special genre tree walking, broadening on empty type, streaming option scope, and that output is opaque session-scoped keys. No contradictions.

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?

Description is detailed and well-structured, front-loading purpose then special cases. Slightly verbose but every sentence adds value; could be marginally tightened without losing clarity.

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

Completeness5/5

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

Given 4 parameters, no output schema, and no annotations, the description fully informs an agent: what it does, how to use each parameter, special behaviors, and expected output (opaque keys for playback). Complete for effective invocation.

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

Parameters5/5

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

Schema coverage is 100%, but description adds significant nuance: explains genre type is special, empty type broadens, includeStreaming only works with genre and appends streaming tracks, and output is opaque keys. Adds meaning beyond schema descriptions.

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 the tool searches Roon music by free-text query, listing specific item types (artist, album, etc.), and distinguishes it from sibling playback tools by mentioning it returns item keys for use with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this when the user names music to find', and instructs to pair with get_tracks_for, play_now, or enqueue_and_play, providing clear guidance on when to use this tool vs alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bestimmaa/roon-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server