rootvine-mcp
rootvine-mcp
一个面向 AI 代理的中立商业解析层。通过 Model Context Protocol 将 Claude、ChatGPT 及其他 AI 代理连接到可信的产品和媒体数据,涵盖从流媒体到收藏版的所有路径。
功能概述
当用户询问 AI 代理“我在哪里可以听 Aphex Twin 的 Windowlicker?”时,RootVine 会在所有主流流媒体、购买和实体平台中解析该查询,并返回带有直接链接的排名结果。
同样的架构可以回答完整的购买需求:流媒体播放、数字购买或查找黑胶唱片。音乐功能现已上线。游戏、书籍、电影、播客和现场活动等垂直领域将在上线后陆续推出。
无广告。无赞助排名。无付费排名。 结果由中立的确定性算法进行排名:信任等级 → 价格 → 可用性 → 时效性 → 商家 ID。佣金率、联盟网络和赞助标记在架构上被排除在排名函数之外。
Related MCP server: sonovault-mcp
快速入门
Claude Desktop
添加到您的 Claude Desktop 配置文件 (~/.claude/claude_desktop_config.json) 中:
{
"mcpServers": {
"rootvine": {
"command": "npx",
"args": ["-y", "rootvine-mcp"]
}
}
}重启 Claude Desktop。现在您可以询问:
“我在哪里可以播放 Ed Sheeran 的 Galway Girl?”
“我在哪里可以听 Aphex Twin 的 Windowlicker?”
“查找 Kendrick Lamar 新专辑的链接”
其他 MCP 客户端
任何兼容 MCP 的客户端都可以通过 stdio 传输使用 rootvine-mcp:
npx rootvine-mcp工具
discover_music
浏览精选音乐合集——排行榜、流派墙、心情、编辑播放列表和艺术家精选。
输入: { chamber?: "by-genre" | "for-this-moment" | "charts" | "by-era" | "spotlights", wall?: string, limit?: number }
模式(由设置的参数决定):
大厅 (Foyer)(无参数)——所有展厅和特色墙的概览
展厅 (Chamber) (
chamber参数) ——列出展厅内的墙(例如所有流派走廊)墙 (Wall) (
wall参数) ——深入查看特定墙的曲目、专辑或艺术家
返回: 带有真实归属的精选合集(例如“由 Deezer 编辑团队精选”、“基于 Last.fm 记录”)。每个条目都链接到一个 BeatsVine 页面,其流媒体和购买链接可通过 resolve_music 获取。
resolve_music
查找流媒体播放、购买或收藏歌曲或专辑的途径。
输入: { slug: "ed-sheeran-galway-girl" }
返回: 涵盖以下内容的排名结果:
流媒体 — Spotify, Apple Music, Tidal, YouTube Music, Deezer
数字购买 — iTunes Store, Amazon Music, Bandcamp
实体媒体 — 黑胶唱片, CD (通过 Amazon), Discogs 收藏列表
每个结果都包含价格(如有)、直接链接以及用于追踪的联盟标签点击 URL。
resolve_game (即将推出)
Steam、PlayStation、Xbox、Nintendo、Epic、GOG、Humble 和 Fanatical 的游戏价格解析。此工具已注册但尚未激活——在游戏垂直领域上线前,它将返回“即将推出”的响应。
find_product
智能路由——自动检测类别并路由到正确的解析器。
输入: { query: "Aphex Twin Windowlicker", category: "auto" }
返回: 目前为音乐结果(流媒体、数字购买、黑胶唱片、CD、收藏版)。游戏、书籍、电影、播客和现场活动门票将在各垂直领域上线时自动路由。
响应格式
所有结果均遵循 RootVine v1 规范:
{
"rootvine": {
"version": "1.0",
"resolver": "beatsvine",
"category": "music"
},
"status": "success",
"query": {
"type": "music",
"artist": "Aphex Twin",
"title": "Windowlicker"
},
"results": [
{
"rank": 1,
"merchant": "Spotify",
"trust_tier": "authoritative",
"price": null,
"url": "https://open.spotify.com/track/...",
"click_url": "https://beatsvine.com/r/abc123",
"type": "stream",
"ranking_reason": {
"code": "FREE_STREAM_T1",
"summary": "Free stream from authoritative source"
}
}
]
}路线图
✅ 音乐解析 — 已上线(流媒体、数字购买、黑胶唱片、CD、收藏版,涵盖 Spotify, Apple Music, iTunes, Amazon, Bandcamp, Discogs, YouTube Music, Tidal, Deezer 等)
✅ 音乐发现 — 已上线(浏览排行榜、流派墙、心情合集、编辑播放列表、艺术家精选)
🔜 游戏 — 数字密钥、实体拷贝和收藏版 (Steam, PlayStation, Xbox, Nintendo, Epic, GOG)
🔜 书籍 — 电子书、有声书、平装书、精装书和特别版 (Amazon, Bookshop.org, Apple Books, Kobo, Audible)
🔜 电影与电视 — 流媒体、租赁、数字购买、DVD、蓝光和 4K 铁盒版
🔜 播客 — Apple Podcasts, Spotify, Pocket Casts 等平台的收听链接
🔜 现场活动 — 演唱会、演出和音乐节门票 (Ticketmaster, Dice, See Tickets)
中立性
RootVine 遵循严格的中立政策:
排名由 信任等级 → 价格 → 可用性 → 时效性 → 商家 ID 决定
佣金率、联盟网络和赞助标记在架构上被排除在排名函数之外
排名逻辑在服务器端运行——此包仅为轻量级客户端
许可证
MIT — © Raging Orangutan Holdings
Available Tools
5 toolsdiscover_musicCharts and collectionsARead-onlyInspect
Browse live charts, genre and mood walls, editorial playlists, artist spotlights, and chart snapshots back to 1946 — "what's trending", "number one in 1994". Charts move weekly: call rather than recall. No arguments gives the chambers and featured walls; year gives that year's snapshots; wall gives its entries, each with a query for resolve_music. Add resolve: true with wall to get number one's links in the same call. RootVine never fabricates. Every link existed at resolved_at. Limits: UK-focused stores, prices in GBP; music only today — games are not live yet. On partial, say which sources didn't answer; on no_results, tell the user plainly — never fall back to guessing a link.
| Name | Required | Description | Default |
|---|---|---|---|
| wall | No | A wall or chart-snapshot slug from an earlier answer (a BeatsVine wall address also works). Lists its entries; on a ranked chart position 1 is number one. Takes priority over `chamber` and `year`. | |
| year | No | Chart snapshots from this year (1946 to now), for questions about the past — 'number one in 1994'. Pass a snapshot's slug back as `wall` for its entries. Takes priority over `chamber`. | |
| limit | No | Max walls, entries or snapshots to return: 10 by default, 30 at most. | |
| chamber | No | Chamber to browse; omit for an overview of all chambers and featured walls. 'by-genre' = genre corridors. 'for-this-moment' = moods and activities. 'charts' = live streaming charts. 'by-era' = decades. 'spotlights' = artist features. | |
| resolve | No | With `wall`: also fetch number one's stream and buy links, in the same call. |
Output Schema
| Name | Required | Description |
|---|---|---|
| top | No | Number one's links, when resolve was asked for |
| mode | Yes | |
| wall | No | |
| year | No | |
| total | Yes | |
| walls | No | |
| years | No | |
| chamber | No | |
| entries | No | |
| chambers | No | |
| top_note | No | |
| snapshots | No | |
| source_url | Yes | |
| resolved_at | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely useful behavior: charts move weekly so call rather than recall, every link existed at resolved_at, no fabrication, UK/GBP scoping, and music-only (games not live). It stops short of describing pagination or the shape of results, but the output schema likely covers returns.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Dense but front-loaded: what it browses, then the call-shape recipes, then trust/limits caveats. Every clause carries signal, though the trust paragraph (RootVine never fabricates, resolved_at) runs long relative to the rest.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained; the description instead covers the gaps that matter — invocation modes, error handling on partial/no_results, geographic/currency limits, and what is not yet live. Nothing needed to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, but the description adds combination semantics the schema does not: passing a snapshot slug back as `wall`, and pairing `resolve: true` with `wall` to get number-one links in one call. Priority ordering is repeated from the schema, so this is a modest lift above baseline rather than a full 5.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (browse) plus concrete resources: live charts, genre/mood walls, editorial playlists, artist spotlights, and historical snapshots back to 1946. It also names resolve_music as the follow-on for the `query` values returned, which cleanly separates it from that sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit invocation recipes: no arguments yields chambers and featured walls, `year` yields that year's snapshots, `wall` yields entries, and `resolve: true` with `wall` fetches number-one links inline. It also states when not to guess and how to handle partial/no_results outcomes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
find_productFind a productARead-onlyInspect
Start here when the category is unclear. Pass the user's words as query; RootVine reads music or games from them (keyword-based — set category when you know it) and answers in that tool's shape. Music is live; games answer "coming soon" for now. RootVine never fabricates. Every link existed at resolved_at. Limits: UK-focused stores, prices in GBP; music only today — games are not live yet. On partial, say which sources didn't answer; on no_results, tell the user plainly — never fall back to guessing a link.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The user's words: 'where can I stream Bad Guy by Billie Eilish', 'Mario Kart on Switch'. | |
| category | No | Set it when you know it; 'auto' (the default) reads it from the words. |
Output Schema
| Name | Required | Description |
|---|---|---|
| game | No | |
| music | No | |
| category | Yes | |
| detected | Yes | true: the category was read from the words — set `category` if it is wrong |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds substantial behavioral context beyond the readOnly/openWorld annotations: 'RootVine never fabricates', 'Every link existed at resolved_at', and specific handling instructions for partial and no_results responses. It also discloses that games are not live yet and that results are UK/GBP-focused. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is information-dense and front-loaded with the key routing guidance. It earns most sentences, but the games-not-live limitation is stated twice ('games answer coming soon' and 'music only today — games are not live yet'), which is minor padding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter tool with an output schema and readOnly/openWorld annotations, the description covers routing behavior, parameter usage, current limitations, geographic scope, and failure-mode handling. Nothing essential for correct selection and invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 meaningful usage meaning: `query` should be the user's raw words used for keyword-based detection, and `category` should be set when known or left to the 'auto' default. This goes beyond the schema's field descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with 'Start here when the category is unclear' and clearly explains that it takes the user's words, detects music or games, and answers in that tool's shape. This distinguishes it from the sibling resolve_* and discover_music tools by establishing it as the routing/entry-point tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states when to use it ('Start here when the category is unclear') and advises setting `category` when known. It also gives useful behavioral guidance for partial/no_results cases. However, it doesn't name explicit alternatives or say what to do when the category is already clear, so there are no direct when-not/alternative exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
resolve_artistArtist discographyARead-onlyInspect
An artist's live profile and discography from BeatsVine, for "what else has X made" or "X's albums". Each release has a query to pass to resolve_music for its links; vinyl, CD and collector editions are album-level, so this is the route to them. Pass the artist's name as query. discography_complete: false means not yet indexed — unknown, not empty. RootVine never fabricates. Every link existed at resolved_at. Limits: UK-focused stores, prices in GBP; music only today — games are not live yet. On partial, say which sources didn't answer; on no_results, tell the user plainly — never fall back to guessing a link.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | Deprecated alias for `query`, kept for older clients. Send exactly one of `query` or `slug`. | |
| query | No | The artist's name in plain words: 'Stromae', 'Billie Eilish'. Also takes a BeatsVine artist address or an `artist/…` query from an earlier answer. |
Output Schema
| Name | Required | Description |
|---|---|---|
| artist | Yes | |
| status | Yes | |
| releases | Yes | |
| resolved_as | Yes | |
| resolved_at | Yes | |
| did_you_mean | Yes | |
| release_count | Yes | |
| discography_complete | Yes | false: BeatsVine has not indexed this artist yet — an empty list means unknown, not none |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the description adds significant context beyond them: 'RootVine never fabricates', 'Every link existed at resolved_at', the meaning of discography_complete: false as unknown not empty, and explicit handling instructions for partial and no_results cases. This enriches the agent's understanding of data reliability and response handling without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is moderately long but every sentence carries weight: purpose, release linkage, index state, data integrity, store limits, and failure handling. It is front-loaded with the core purpose and then layers constraints, so the structure is effective and not wasteful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists, the description covers all essential operational aspects: how to call it (artist name in query), what the output implies (each release has a query), limitations (UK stores, GBP, music only), and behavior on partial/no_results. The agent can use it correctly without missing critical context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already explains both parameters. The description reinforces that the artist name goes in `query` and that slug is deprecated, but it does not introduce new parameter meaning beyond what the schema provides. Baseline 3 applies because the description adds little extra semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb+resource: 'An artist's live profile and discography from BeatsVine'. It names the intended queries ('what else has X made' or 'X's albums') and distinguishes from siblings by pointing out that each release carries a query for resolve_music and that album-level editions are routed here.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context on when to use the tool (artist discography needs) and even directs album-level editions to this route. It also notes that games are not live, hinting at resolve_game. However, it does not explicitly state 'use resolve_music for individual tracks' or when NOT to use this tool, though the mention of resolve_music implies a division of labor.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
resolve_gameGame prices (coming soon)ARead-onlyInspect
Where to buy a video game. Not live yet: every call returns an explicit "coming soon" — no links, no prices — and contacts no store. Tell the user plainly that games aren't supported yet; never guess a store link or a price. For music, use resolve_music. RootVine never fabricates. Every link existed at resolved_at. Limits: UK-focused stores, prices in GBP; music only today — games are not live yet. On partial, say which sources didn't answer; on no_results, tell the user plainly — never fall back to guessing a link.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | Deprecated alias for `query`, kept for older clients. Send exactly one of `query` or `slug`. | |
| query | No | The game's name in plain words: 'Elden Ring'. |
Output Schema
| Name | Required | Description |
|---|---|---|
| live | Yes | false: games are not live yet — there are no links or prices to give |
| query | Yes | |
| status | Yes | |
| message | Yes | |
| results | Yes | |
| resolved_at | Yes | |
| response_id | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses key behaviors beyond the annotations: it states every call returns an explicit 'coming soon' with no links/prices and no store contact; it adds the 'RootVine never fabricates' truthfulness guarantee; and it explains the UK/GBP scope and error-response expectations. Annotations only say readOnlyHint and openWorldHint, so the description carries significant extra behavioral context with no contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is reasonably concise and front-loaded with purpose and status. There is slight redundancy ('not live yet' appears three times, and 'never guess' appears twice), but overall each sentence contributes meaningful guidance. It earns a 4 rather than a 5 due to minor repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a stub tool with an output schema, the description is notably complete. It covers the tool's current status, user-interaction expectations, limitations (UK-focused, GBP), error-handling behavior, and sibling routing. There is no significant missing information an agent would need to call or respond correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with both parameters (slug and query) already described in the schema. The description does not add any new parameter-specific information beyond what the schema provides, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with 'Where to buy a video game', a specific verb+resource statement. It immediately distinguishes itself from resolve_music ('For music, use resolve_music') and explicitly notes the tool is not live yet, so an agent knows exactly what this tool is (or will be) for and how it differs from siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit guidance: 'Not live yet' tells the agent not to expect real results; 'For music, use resolve_music' names the specific alternative; and it provides direct instructions for handling partial and no_results responses ('say which sources didn't answer', 'never fall back to guessing a link'). This is comprehensive usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
resolve_musicMusic linksARead-onlyInspect
Live stream, buy and collect links for a song or album — streaming services, digital stores, vinyl and CD — ranked by trust, price and availability, never by commission. Call it rather than recall: links and prices change; a guessed link 404s. Pass the user's words as query ("galway girl by ed sheeran"); never build slugs. On a miss, did_you_mean lists close matches, each with a query to pass back; when resolved_as.corrected is true, tell the user which recording is shown. RootVine never fabricates. Every link existed at resolved_at. Limits: UK-focused stores, prices in GBP; music only today — games are not live yet. On partial, say which sources didn't answer; on no_results, tell the user plainly — never fall back to guessing a link.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | Deprecated alias for `query`, kept for older clients. Send exactly one of `query` or `slug`. | |
| query | No | What to look up, in the user's own words: 'galway girl by ed sheeran', 'Abbey Road vinyl'. Also takes a BeatsVine page address or a `query` value from an earlier answer. Do not build slugs. |
Output Schema
| Name | Required | Description |
|---|---|---|
| kind | Yes | |
| title | Yes | |
| artist | Yes | |
| status | Yes | |
| results | Yes | |
| page_url | Yes | The BeatsVine page, only when it is confirmed to exist |
| warnings | Yes | |
| cover_art | Yes | |
| resolved_as | Yes | |
| resolved_at | Yes | Every link existed at this time |
| response_id | Yes | |
| ttl_seconds | Yes | |
| did_you_mean | Yes | |
| partial_sources | Yes | Sources that did not answer: say so when not empty |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds substantial behavioral context beyond the readOnlyHint and openWorldHint annotations: links existed at resolved_at, RootVine never fabricates, rankings ignore commissions, results are UK-focused with GBP prices, and edge cases like partial/no_results have explicit handling. Nothing contradicts the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is dense but every sentence earns its place, covering purpose, usage, reliability, limits, and failure behavior. It is front-loaded with the core purpose before diving into details, and it avoids filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity and the existence of an output schema, the description still provides complete operational context: how to call it, what to do with did_you_mean and corrected results, limits, and how to surface failures. An agent can correctly invoke and interpret the response without additional information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by showing natural-language examples, allowing a BeatsVine page address or a prior query value, and repeatedly instructing 'never build slugs.' This is useful but not dramatically beyond what the schema already documents.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description defines the tool's core job with a specific verb and resource: resolving a song or album into live stream/buy/collect links across services and formats. It further distinguishes itself from siblings by scoping to 'music only today — games are not live yet' and to 'a song or album,' separating it from resolve_artist and resolve_game.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives strong when-to-use guidance: 'Call it rather than recall: links and prices change; a guessed link 404s.' It also provides behavioral instructions for miss, corrected, partial, and no-results cases. However, it does not explicitly mention alternatives like discover_music or resolve_artist, though the 'song or album' and 'music only' scope implicitly excludes them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
5 tool updates
v1.4.0- Changed
discover_music7 fields changed- changed
Input schema / properties / chamber / descriptionPrevious value: -"Chamber to browse. Omit for a top-level overview of all chambers and featured walls. 'by-genre' = genre corridors (house, hip-hop, jazz, etc.). 'for-this-moment' = mood and activity walls (chill, focus, workout). 'charts' = live streaming charts. 'by-era' = decades and golden eras. 'spotlights' = editor-led artist features."New value: +"Chamber to browse; omit for an overview of all chambers and featured walls. 'by-genre' = genre corridors. 'for-this-moment' = moods and activities. 'charts' = live streaming charts. 'by-era' = decades. 'spotlights' = artist features." - changed
Input schema / properties / limit / descriptionPrevious value: -"Max items to return. Default 10, max 30. Applies to walls (foyer/chamber mode), entries (wall mode) or snapshots (year mode)."New value: +"Max walls, entries or snapshots to return: 10 by default, 30 at most." - added
Input schema / properties / resolveAdded value: +{ + "description": "With `wall`: also fetch number one's stream and buy links, in the same call.", + "type": "boolean" +} - changed
Input schema / properties / wall / descriptionPrevious value: -"Wall slug to drill into. If set, returns the wall's track/album/artist entries. Takes priority over `chamber`. Example: 'lastfm-top-electronic-tracks', 'deezer-90s-hits'. Slugs are returned in the foyer and chamber responses."New value: +"A wall or chart-snapshot slug from an earlier answer (a BeatsVine wall address also works). Lists its entries; on a ranked chart position 1 is number one. Takes priority over `chamber` and `year`." - added
Input schema / properties / wall / maxLengthAdded value: +500 - changed
Input schema / properties / year / descriptionPrevious value: -"Browse archived chart snapshots from this year. Use for questions about the past — 'what was number one in 1994', 'what was in the charts when I was born'. Archives run from 1946 to the present. Returns snapshot slugs; pass one back as `wall` to get the ranked entries, where position 1 is the number one. Takes priority over `chamber`."New value: +"Chart snapshots from this year (1946 to now), for questions about the past — 'number one in 1994'. Pass a snapshot's slug back as `wall` for its entries. Takes priority over `chamber`." - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "chamber": { + "additionalProperties": {}, + "properties": { + "name": { + "type": "string" + }, + "slug": { + "type": "string" + }, + "tagline": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "slug", + "name", + "tagline" + ], + "type": "object" + }, + "chambers": { + "items": { + "additionalProperties": {}, + "properties": { + "name": { + "type": "string" + }, + "slug": { + "type": "string" + }, + "tagline": { + "type": [ + "string", + "null" + ] + }, + "wall_count": { + "type": "number" + } + }, + "required": [ + "slug", + "name", + "tagline", + "wall_count" + ], + "type": "object" + }, + "type": "array" + }, + "entries": { + "items": { + "additionalProperties": {}, + "properties": { + "artist": { + "type": [ + "string", + "null" + ] + }, + "cover_url": { + "type": [ + "string", + "null" + ] + }, + "kind": { + "anyOf": [ + { + "enum": [ + "track", + "album", + "artist" + ], + "type": "string" + }, + { + "type": "null" + } + ] + }, + "page_url": { + "type": [ + "string", + "null" + ] + }, + "position": { + "type": "number" + }, + "preview_url": { + "type": [ + "string", + "null" + ] + }, + "query": { + "description": "Pass to resolve_music (resolve_artist for an artist) for links; null: no BeatsVine page yet", + "type": [ + "string", + "null" + ] + }, + "title": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "position", + "title", + "artist", + "kind", + "query", + "page_url", + "cover_url", + "preview_url" + ], + "type": "object" + }, + "type": "array" + }, + "mode": { + "enum": [ + "foyer", + "chamber", + "wall", + "archives" + ], + "type": "string" + }, + "resolved_at": { + "type": "string" + }, + "snapshots": { + "items": { + "additionalProperties": {}, + "properties": { + "entry_count": { + "type": "number" + }, + "name": { + "type": "string" + }, + "page_url": { + "type": "string" + }, + "publication": { + "anyOf": [ + { + "additionalProperties": {}, + "description": "How much of the chart BeatsVine shows: 'full'; 'headline' — the number one only, the rest at full_chart_url; 'yearly-number-ones' — each year's best seller, no overall number one", + "properties": { + "chart_owner": { + "type": [ + "string", + "null" + ] + }, + "full_chart_url": { + "type": [ + "string", + "null" + ] + }, + "mode": { + "type": "string" + }, + "note": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "mode", + "chart_owner", + "full_chart_url", + "note" + ], + "type": "object" + }, + { + "type": "null" + } + ] + }, + "slug": { + "description": "Pass as `wall`, with resolve: true for number one's links", + "type": "string" + }, + "week": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "slug", + "name", + "week", + "entry_count", + "page_url", + "publication" + ], + "type": "object" + }, + "type": "array" + }, + "source_url": { + "type": [ + "string", + "null" + ] + }, + "top": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "artist": { + "type": [ + "string", + "null" + ] + }, + "cover_art": { + "type": [ + "string", + "null" + ] + }, + "did_you_mean": { + "items": { + "additionalProperties": {}, + "properties": { + "artist": { + "type": [ + "string", + "null" + ] + }, + "kind": { + "enum": [ + "track", + "album", + "artist" + ], + "type": "string" + }, + "page_url": { + "type": [ + "string", + "null" + ] + }, + "query": { + "description": "Pass back as `query` to open exactly this", + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "title", + "artist", + "kind", + "query", + "page_url" + ], + "type": "object" + }, + "type": "array" + }, + "kind": { + "anyOf": [ + { + "enum": [ + "track", + "album" + ], + "type": "string" + }, + { + "type": "null" + } + ] + }, + "page_url": { + "description": "The BeatsVine page, only when it is confirmed to exist", + "type": [ + "string", + "null" + ] + }, + "partial_sources": { + "description": "Sources that did not answer: say so when not empty", + "items": { + "type": "string" + }, + "type": "array" + }, + "resolved_as": { + "additionalProperties": {}, + "properties": { + "corrected": { + "description": "The answer is for different words than asked: tell the user what is shown", + "type": "boolean" + }, + "note": { + "type": [ + "string", + "null" + ] + }, + "query": { + "type": [ + "string", + "null" + ] + }, + "via": { + "anyOf": [ + { + "enum": [ + "direct", + "catalogue_search", + "live_lookup" + ], + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "query", + "via", + "corrected", + "note" + ], + "type": "object" + }, + "resolved_at": { + "description": "Every link existed at this time", + "type": "string" + }, + "response_id": { + "type": [ + "string", + "null" + ] + }, + "results": { + "items": { + "additionalProperties": {}, + "properties": { + "availability": { + "enum": [ + "in_stock", + "preorder", + "available", + "unknown" + ], + "type": "string" + }, + "click_url": { + "description": "The link to give the user", + "type": "string" + }, + "edition": { + "type": "string" + }, + "merchant": { + "type": "string" + }, + "merchant_id": { + "type": "string" + }, + "price": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "amount": { + "type": "number" + }, + "currency": { + "type": "string" + } + }, + "required": [ + "amount", + "currency" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "description": "null when no price is listed — never zero, never free" + }, + "price_freshness": { + "type": "string" + }, + "rank": { + "type": "number" + }, + "ranking_reason": { + "additionalProperties": {}, + "properties": { + "code": { + "type": "string" + }, + "summary": { + "type": "string" + } + }, + "required": [ + "code", + "summary" + ], + "type": "object" + }, + "trust_tier": { + "enum": [ + "authoritative", + "verified", + "listed" + ], + "type": "string" + }, + "type": { + "enum": [ + "purchase", + "stream", + "subscription" + ], + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "rank", + "merchant", + "merchant_id", + "type", + "trust_tier", + "availability", + "price", + "click_url", + "url", + "ranking_reason" + ], + "type": "object" + }, + "type": "array" + }, + "status": { + "enum": [ + "success", + "partial", + "no_results" + ], + "type": "string" + }, + "title": { + "type": [ + "string", + "null" + ] + }, + "ttl_seconds": { + "type": [ + "number", + "null" + ] + }, + "warnings": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "status", + "artist", + "title", + "kind", + "results", + "partial_sources", + "warnings", + "resolved_as", + "did_you_mean", + "page_url", + "cover_art", + "response_id", + "resolved_at", + "ttl_seconds" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "description": "Number one's links, when resolve was asked for" + }, + "top_note": { + "type": [ + "string", + "null" + ] + }, + "total": { + "type": [ + "number", + "null" + ] + }, + "wall": { + "additionalProperties": {}, + "properties": { + "attribution": { + "type": [ + "string", + "null" + ] + }, + "description": { + "type": [ + "string", + "null" + ] + }, + "entity_type": { + "type": [ + "string", + "null" + ] + }, + "name": { + "type": "string" + }, + "page_url": { + "type": "string" + }, + "publication": { + "anyOf": [ + { + "additionalProperties": {}, + "description": "How much of the chart BeatsVine shows: 'full'; 'headline' — the number one only, the rest at full_chart_url; 'yearly-number-ones' — each year's best seller, no overall number one", + "properties": { + "chart_owner": { + "type": [ + "string", + "null" + ] + }, + "full_chart_url": { + "type": [ + "string", + "null" + ] + }, + "mode": { + "type": "string" + }, + "note": { + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "mode", + "chart_owner", + "full_chart_url", + "note" + ], + "type": "object" + }, + { + "type": "null" + } + ] + }, + "slug": { + "type": "string" + } + }, + "required": [ + "slug", + "name", + "description", + "entity_type", + "attribution", + "page_url", + "publication" + ], + "type": "object" + }, + "walls": { + "items": { + "additionalProperties": {}, + "properties": { + "attribution": { + "type": [ + "string", + "null" + ] + }, + "description": { + "type": [ + "string", + "null" + ] + }, + "entry_count": { + "type": "number" + }, + "name": { + "type": "string" + }, + "page_url": { + "type": "string" + }, + "slug": { + "description": "Pass as `wall` to list its entries", + "type": "string" + } + }, + "required": [ + "slug", + "name", + "description", + "entry_count", + "attribution", + "page_url" + ], + "type": "object" + }, + "type": "array" + }, + "year": { + "type": [ + "number", + "null" + ] + }, + "years": { + "items": { + "type": "number" + }, + "type": "array" + } + }, + "required": [ + "mode", + "source_url", + "resolved_at", + "total" + ], + "type": "object" +}
- Changed
find_product4 fields changed- changed
Input schema / properties / category / descriptionPrevious value: -"Product category. Use 'auto' (default) to let RootVine detect the category automatically."New value: +"Set it when you know it; 'auto' (the default) reads it from the words." - changed
Input schema / properties / query / descriptionPrevious value: -"A natural language product query. Examples: 'Aphex Twin Windowlicker', 'Elden Ring DLC', 'where can I stream Bad Guy by Billie Eilish'"New value: +"The user's words: 'where can I stream Bad Guy by Billie Eilish', 'Mario Kart on Switch'." - added
Input schema / properties / query / maxLengthAdded value: +500 - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "category": { + "enum": [ + "music", + "game" + ], + "type": "string" + }, + "detected": { + "description": "true: the category was read from the words — set `category` if it is wrong", + "type": "boolean" + }, + "game": { + "additionalProperties": {}, + "properties": { + "live": { + "description": "false: games are not live yet — there are no links or prices to give", + "type": "boolean" + }, + "message": { + "type": [ + "string", + "null" + ] + }, + "query": { + "type": "string" + }, + "resolved_at": { + "type": "string" + }, + "response_id": { + "type": [ + "string", + "null" + ] + }, + "results": { + "items": { + "additionalProperties": {}, + "properties": { + "availability": { + "enum": [ + "in_stock", + "preorder", + "available", + "unknown" + ], + "type": "string" + }, + "click_url": { + "description": "The link to give the user", + "type": "string" + }, + "edition": { + "type": "string" + }, + "merchant": { + "type": "string" + }, + "merchant_id": { + "type": "string" + }, + "price": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "amount": { + "type": "number" + }, + "currency": { + "type": "string" + } + }, + "required": [ + "amount", + "currency" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "description": "null when no price is listed — never zero, never free" + }, + "price_freshness": { + "type": "string" + }, + "rank": { + "type": "number" + }, + "ranking_reason": { + "additionalProperties": {}, + "properties": { + "code": { + "type": "string" + }, + "summary": { + "type": "string" + } + }, + "required": [ + "code", + "summary" + ], + "type": "object" + }, + "trust_tier": { + "enum": [ + "authoritative", + "verified", + "listed" + ], + "type": "string" + }, + "type": { + "enum": [ + "purchase", + "stream", + "subscription" + ], + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "rank", + "merchant", + "merchant_id", + "type", + "trust_tier", + "availability", + "price", + "click_url", + "url", + "ranking_reason" + ], + "type": "object" + }, + "type": "array" + }, + "status": { + "enum": [ + "coming_soon", + "success", + "partial", + "no_results" + ], + "type": "string" + } + }, + "required": [ + "status", + "live", + "query", + "message", + "results", + "response_id", + "resolved_at" + ], + "type": "object" + }, + "music": { + "additionalProperties": {}, + "properties": { + "artist": { + "type": [ + "string", + "null" + ] + }, + "cover_art": { + "type": [ + "string", + "null" + ] + }, + "did_you_mean": { + "items": { + "additionalProperties": {}, + "properties": { + "artist": { + "type": [ + "string", + "null" + ] + }, + "kind": { + "enum": [ + "track", + "album", + "artist" + ], + "type": "string" + }, + "page_url": { + "type": [ + "string", + "null" + ] + }, + "query": { + "description": "Pass back as `query` to open exactly this", + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "title", + "artist", + "kind", + "query", + "page_url" + ], + "type": "object" + }, + "type": "array" + }, + "kind": { + "anyOf": [ + { + "enum": [ + "track", + "album" + ], + "type": "string" + }, + { + "type": "null" + } + ] + }, + "page_url": { + "description": "The BeatsVine page, only when it is confirmed to exist", + "type": [ + "string", + "null" + ] + }, + "partial_sources": { + "description": "Sources that did not answer: say so when not empty", + "items": { + "type": "string" + }, + "type": "array" + }, + "resolved_as": { + "additionalProperties": {}, + "properties": { + "corrected": { + "description": "The answer is for different words than asked: tell the user what is shown", + "type": "boolean" + }, + "note": { + "type": [ + "string", + "null" + ] + }, + "query": { + "type": [ + "string", + "null" + ] + }, + "via": { + "anyOf": [ + { + "enum": [ + "direct", + "catalogue_search", + "live_lookup" + ], + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "query", + "via", + "corrected", + "note" + ], + "type": "object" + }, + "resolved_at": { + "description": "Every link existed at this time", + "type": "string" + }, + "response_id": { + "type": [ + "string", + "null" + ] + }, + "results": { + "items": { + "additionalProperties": {}, + "properties": { + "availability": { + "enum": [ + "in_stock", + "preorder", + "available", + "unknown" + ], + "type": "string" + }, + "click_url": { + "description": "The link to give the user", + "type": "string" + }, + "edition": { + "type": "string" + }, + "merchant": { + "type": "string" + }, + "merchant_id": { + "type": "string" + }, + "price": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "amount": { + "type": "number" + }, + "currency": { + "type": "string" + } + }, + "required": [ + "amount", + "currency" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "description": "null when no price is listed — never zero, never free" + }, + "price_freshness": { + "type": "string" + }, + "rank": { + "type": "number" + }, + "ranking_reason": { + "additionalProperties": {}, + "properties": { + "code": { + "type": "string" + }, + "summary": { + "type": "string" + } + }, + "required": [ + "code", + "summary" + ], + "type": "object" + }, + "trust_tier": { + "enum": [ + "authoritative", + "verified", + "listed" + ], + "type": "string" + }, + "type": { + "enum": [ + "purchase", + "stream", + "subscription" + ], + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "rank", + "merchant", + "merchant_id", + "type", + "trust_tier", + "availability", + "price", + "click_url", + "url", + "ranking_reason" + ], + "type": "object" + }, + "type": "array" + }, + "status": { + "enum": [ + "success", + "partial", + "no_results" + ], + "type": "string" + }, + "title": { + "type": [ + "string", + "null" + ] + }, + "ttl_seconds": { + "type": [ + "number", + "null" + ] + }, + "warnings": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "status", + "artist", + "title", + "kind", + "results", + "partial_sources", + "warnings", + "resolved_as", + "did_you_mean", + "page_url", + "cover_art", + "response_id", + "resolved_at", + "ttl_seconds" + ], + "type": "object" + } + }, + "required": [ + "category", + "detected" + ], + "type": "object" +}
- Changed
resolve_artist5 fields changed- added
Input schema / properties / queryAdded value: +{ + "description": "The artist's name in plain words: 'Stromae', 'Billie Eilish'. Also takes a BeatsVine artist address or an `artist/…` query from an earlier answer.", + "maxLength": 500, + "type": "string" +} - changed
Input schema / properties / slug / descriptionPrevious value: -"The BeatsVine artist slug, lowercase and hyphenated: 'stromae', 'radiohead', 'ed-sheeran'. Slugs keep letters of any script, so non-Latin names are valid. An 'artist/name' form is also accepted, since that is what BeatsVine's search returns for artist hits."New value: +"Deprecated alias for `query`, kept for older clients. Send exactly one of `query` or `slug`." - added
Input schema / properties / slug / maxLengthAdded value: +500 - removed
Input schema / requiredRemoved value: -[ - "slug" -] - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "artist": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "genres": { + "items": { + "type": "string" + }, + "type": "array" + }, + "name": { + "type": "string" + }, + "page_url": { + "type": "string" + }, + "query": { + "description": "Pass back to resolve_artist to open this artist", + "type": "string" + } + }, + "required": [ + "name", + "query", + "page_url", + "genres" + ], + "type": "object" + }, + { + "type": "null" + } + ] + }, + "did_you_mean": { + "items": { + "additionalProperties": {}, + "properties": { + "artist": { + "type": [ + "string", + "null" + ] + }, + "kind": { + "enum": [ + "track", + "album", + "artist" + ], + "type": "string" + }, + "page_url": { + "type": [ + "string", + "null" + ] + }, + "query": { + "description": "Pass back as `query` to open exactly this", + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "title", + "artist", + "kind", + "query", + "page_url" + ], + "type": "object" + }, + "type": "array" + }, + "discography_complete": { + "description": "false: BeatsVine has not indexed this artist yet — an empty list means unknown, not none", + "type": [ + "boolean", + "null" + ] + }, + "release_count": { + "type": [ + "number", + "null" + ] + }, + "releases": { + "items": { + "additionalProperties": {}, + "properties": { + "cover_url": { + "type": [ + "string", + "null" + ] + }, + "page_url": { + "type": [ + "string", + "null" + ] + }, + "query": { + "description": "Pass to resolve_music for this release's links", + "type": "string" + }, + "title": { + "type": "string" + }, + "type": { + "type": [ + "string", + "null" + ] + }, + "year": { + "type": [ + "number", + "null" + ] + } + }, + "required": [ + "title", + "type", + "year", + "query", + "page_url", + "cover_url" + ], + "type": "object" + }, + "type": "array" + }, + "resolved_as": { + "additionalProperties": {}, + "properties": { + "corrected": { + "description": "The answer is for different words than asked: tell the user what is shown", + "type": "boolean" + }, + "note": { + "type": [ + "string", + "null" + ] + }, + "query": { + "type": [ + "string", + "null" + ] + }, + "via": { + "anyOf": [ + { + "enum": [ + "direct", + "catalogue_search", + "live_lookup" + ], + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "query", + "via", + "corrected", + "note" + ], + "type": "object" + }, + "resolved_at": { + "type": "string" + }, + "status": { + "enum": [ + "success", + "no_results" + ], + "type": "string" + } + }, + "required": [ + "status", + "artist", + "discography_complete", + "release_count", + "releases", + "resolved_as", + "did_you_mean", + "resolved_at" + ], + "type": "object" +}
- Changed
resolve_game5 fields changed- added
Input schema / properties / queryAdded value: +{ + "description": "The game's name in plain words: 'Elden Ring'.", + "maxLength": 500, + "type": "string" +} - changed
Input schema / properties / slug / descriptionPrevious value: -"The game slug. Format: game-title (lowercase, hyphenated). Example: 'elden-ring'"New value: +"Deprecated alias for `query`, kept for older clients. Send exactly one of `query` or `slug`." - added
Input schema / properties / slug / maxLengthAdded value: +500 - removed
Input schema / requiredRemoved value: -[ - "slug" -] - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "live": { + "description": "false: games are not live yet — there are no links or prices to give", + "type": "boolean" + }, + "message": { + "type": [ + "string", + "null" + ] + }, + "query": { + "type": "string" + }, + "resolved_at": { + "type": "string" + }, + "response_id": { + "type": [ + "string", + "null" + ] + }, + "results": { + "items": { + "additionalProperties": {}, + "properties": { + "availability": { + "enum": [ + "in_stock", + "preorder", + "available", + "unknown" + ], + "type": "string" + }, + "click_url": { + "description": "The link to give the user", + "type": "string" + }, + "edition": { + "type": "string" + }, + "merchant": { + "type": "string" + }, + "merchant_id": { + "type": "string" + }, + "price": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "amount": { + "type": "number" + }, + "currency": { + "type": "string" + } + }, + "required": [ + "amount", + "currency" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "description": "null when no price is listed — never zero, never free" + }, + "price_freshness": { + "type": "string" + }, + "rank": { + "type": "number" + }, + "ranking_reason": { + "additionalProperties": {}, + "properties": { + "code": { + "type": "string" + }, + "summary": { + "type": "string" + } + }, + "required": [ + "code", + "summary" + ], + "type": "object" + }, + "trust_tier": { + "enum": [ + "authoritative", + "verified", + "listed" + ], + "type": "string" + }, + "type": { + "enum": [ + "purchase", + "stream", + "subscription" + ], + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "rank", + "merchant", + "merchant_id", + "type", + "trust_tier", + "availability", + "price", + "click_url", + "url", + "ranking_reason" + ], + "type": "object" + }, + "type": "array" + }, + "status": { + "enum": [ + "coming_soon", + "success", + "partial", + "no_results" + ], + "type": "string" + } + }, + "required": [ + "status", + "live", + "query", + "message", + "results", + "response_id", + "resolved_at" + ], + "type": "object" +}
- Changed
resolve_music5 fields changed- added
Input schema / properties / queryAdded value: +{ + "description": "What to look up, in the user's own words: 'galway girl by ed sheeran', 'Abbey Road vinyl'. Also takes a BeatsVine page address or a `query` value from an earlier answer. Do not build slugs.", + "maxLength": 500, + "type": "string" +} - changed
Input schema / properties / slug / descriptionPrevious value: -"The BeatsVine page slug for the track or album. Format: artist-name-song-title, lowercase and hyphenated. Slugs keep letters of any script, so non-Latin titles are valid: 'ed-sheeran-galway-girl', 'ヨルシカ-火星人'. Latin accents are folded to their base letter ('Rosalía Despechá' → 'rosalia-despecha'), and punctuation is dropped. Pass the slug undecoded — do not percent-encode it yourself."New value: +"Deprecated alias for `query`, kept for older clients. Send exactly one of `query` or `slug`." - added
Input schema / properties / slug / maxLengthAdded value: +500 - removed
Input schema / requiredRemoved value: -[ - "slug" -] - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": {}, + "properties": { + "artist": { + "type": [ + "string", + "null" + ] + }, + "cover_art": { + "type": [ + "string", + "null" + ] + }, + "did_you_mean": { + "items": { + "additionalProperties": {}, + "properties": { + "artist": { + "type": [ + "string", + "null" + ] + }, + "kind": { + "enum": [ + "track", + "album", + "artist" + ], + "type": "string" + }, + "page_url": { + "type": [ + "string", + "null" + ] + }, + "query": { + "description": "Pass back as `query` to open exactly this", + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "title", + "artist", + "kind", + "query", + "page_url" + ], + "type": "object" + }, + "type": "array" + }, + "kind": { + "anyOf": [ + { + "enum": [ + "track", + "album" + ], + "type": "string" + }, + { + "type": "null" + } + ] + }, + "page_url": { + "description": "The BeatsVine page, only when it is confirmed to exist", + "type": [ + "string", + "null" + ] + }, + "partial_sources": { + "description": "Sources that did not answer: say so when not empty", + "items": { + "type": "string" + }, + "type": "array" + }, + "resolved_as": { + "additionalProperties": {}, + "properties": { + "corrected": { + "description": "The answer is for different words than asked: tell the user what is shown", + "type": "boolean" + }, + "note": { + "type": [ + "string", + "null" + ] + }, + "query": { + "type": [ + "string", + "null" + ] + }, + "via": { + "anyOf": [ + { + "enum": [ + "direct", + "catalogue_search", + "live_lookup" + ], + "type": "string" + }, + { + "type": "null" + } + ] + } + }, + "required": [ + "query", + "via", + "corrected", + "note" + ], + "type": "object" + }, + "resolved_at": { + "description": "Every link existed at this time", + "type": "string" + }, + "response_id": { + "type": [ + "string", + "null" + ] + }, + "results": { + "items": { + "additionalProperties": {}, + "properties": { + "availability": { + "enum": [ + "in_stock", + "preorder", + "available", + "unknown" + ], + "type": "string" + }, + "click_url": { + "description": "The link to give the user", + "type": "string" + }, + "edition": { + "type": "string" + }, + "merchant": { + "type": "string" + }, + "merchant_id": { + "type": "string" + }, + "price": { + "anyOf": [ + { + "additionalProperties": {}, + "properties": { + "amount": { + "type": "number" + }, + "currency": { + "type": "string" + } + }, + "required": [ + "amount", + "currency" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "description": "null when no price is listed — never zero, never free" + }, + "price_freshness": { + "type": "string" + }, + "rank": { + "type": "number" + }, + "ranking_reason": { + "additionalProperties": {}, + "properties": { + "code": { + "type": "string" + }, + "summary": { + "type": "string" + } + }, + "required": [ + "code", + "summary" + ], + "type": "object" + }, + "trust_tier": { + "enum": [ + "authoritative", + "verified", + "listed" + ], + "type": "string" + }, + "type": { + "enum": [ + "purchase", + "stream", + "subscription" + ], + "type": "string" + }, + "url": { + "type": "string" + } + }, + "required": [ + "rank", + "merchant", + "merchant_id", + "type", + "trust_tier", + "availability", + "price", + "click_url", + "url", + "ranking_reason" + ], + "type": "object" + }, + "type": "array" + }, + "status": { + "enum": [ + "success", + "partial", + "no_results" + ], + "type": "string" + }, + "title": { + "type": [ + "string", + "null" + ] + }, + "ttl_seconds": { + "type": [ + "number", + "null" + ] + }, + "warnings": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "required": [ + "status", + "artist", + "title", + "kind", + "results", + "partial_sources", + "warnings", + "resolved_as", + "did_you_mean", + "page_url", + "cover_art", + "response_id", + "resolved_at", + "ttl_seconds" + ], + "type": "object" +}
3 tool updates
v1.3.1- Changed
discover_music2 fields changed- changed
Input schema / properties / limit / descriptionPrevious value: -"Max items to return. Default 10, max 30. Applies to walls (foyer/chamber mode) or entries (wall mode)."New value: +"Max items to return. Default 10, max 30. Applies to walls (foyer/chamber mode), entries (wall mode) or snapshots (year mode)." - added
Input schema / properties / yearAdded value: +{ + "description": "Browse archived chart snapshots from this year. Use for questions about the past — 'what was number one in 1994', 'what was in the charts when I was born'. Archives run from 1946 to the present. Returns snapshot slugs; pass one back as `wall` to get the ranked entries, where position 1 is the number one. Takes priority over `chamber`.", + "maximum": 2100, + "minimum": 1946, + "type": "integer" +}
- Added
resolve_artist - Changed
resolve_music1 field changed- changed
Input schema / properties / slug / descriptionPrevious value: -"The BeatsVine page slug for the track or album. Format: artist-name-song-title (lowercase, hyphenated). Example: 'ed-sheeran-galway-girl'"New value: +"The BeatsVine page slug for the track or album. Format: artist-name-song-title, lowercase and hyphenated. Slugs keep letters of any script, so non-Latin titles are valid: 'ed-sheeran-galway-girl', 'ヨルシカ-火星人'. Latin accents are folded to their base letter ('Rosalía Despechá' → 'rosalia-despecha'), and punctuation is dropped. Pass the slug undecoded — do not percent-encode it yourself."
4 tool updates
- Added
discover_music - Changed
find_product1 field changed- removed
Input schema / additionalPropertiesRemoved value: -false
- Changed
resolve_game1 field changed- removed
Input schema / additionalPropertiesRemoved value: -false
- Changed
resolve_music1 field changed- removed
Input schema / additionalPropertiesRemoved value: -false
3 tool updates
v1.0.1- First observed
find_product - First observed
resolve_game - First observed
resolve_music
TDQS
Scored across 5 tools
Each tool has a distinct purpose: resolving music links, resolving games (placeholder), discovering charts, resolving artists, and routing by category. find_product overlaps slightly with resolve_music and resolve_game as a meta-router, but its 'unclear category' guidance mitigates confusion. No two tools are indistinguishable.
All tool names follow a consistent snake_case verb_noun pattern: resolve_music, resolve_game, resolve_artist, discover_music, find_product. The verbs (resolve, discover, find) are clear and appropriate. No mixing of conventions.
Five tools is well-scoped for a music/game discovery and link resolution service. Each tool earns its place: three resolvers, one discoverer, and one router. Neither thin nor excessive.
For the current music-only scope, the surface is nearly complete: resolving songs/albums, discovering charts/playlists, and artist discographies. Minor gaps include album tracklists and the non-functional game resolution (explicitly marked 'coming soon'). Agents can work around these limitations.
Maintenance
Related MCP Connectors
Music marketing for AI agents: free Smart Links, promotion campaigns, analytics, and distribution.
Create geo-targeted affiliate smart links, pull analytics, and rewrite YouTube descriptions.
The media memory layer for AI agents and their humans. Your AI client gets 29 tools to search your collection, add items, update ratings, preview music, and find patterns across everything you've read, watched, and listened to.
Search, analyze, and discover commercially released music using sonic intelligence.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to search, license, and pay for rights-clean music per use, returning a verifiable license certificate.5MIT

sonovault-mcpofficial
AlicenseAqualityAmaintenanceProvides access to the SonoVault music metadata API, enabling search and retrieval of information about 90M+ tracks, artists, labels, and releases, including ISRC, ISWC, and cross-platform IDs.15243 npmMIT
Dynamoi MCPofficial
AlicenseNot gradedqualityBmaintenanceLets AI agents help artists and labels prepare releases for promotion by creating Smart Links, checking campaign readiness, and managing platform connections.67 npm3MIT- FlicenseNot gradedqualityDmaintenanceEnables music search, metadata retrieval, local audio analysis (tempo, key, energy), recommendations, song recognition, and classical work resolution via Spotify, Last.fm, AudD, MusicBrainz, and Songkick APIs.-