A
licenseB
qualityD
maintenanceMachine-readable merchant verification infrastructure for AI shopping agents and agentic commerce systems.
1
3
MIT
rootvine-mcp
Server Details
Neutral commerce resolution for AI agents — music live, ranked by trust, never by commission.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- RagingOrangutan/rootvine-mcp
- GitHub Stars
- 3
- Server Listing
- rootvine-mcp
TDQS
A4.4/5.0
Scored across 5 tools
Disambiguation4/5
Each tool targets a distinct responsibility: browsing charts, routing unclear queries, artist discography, game lookup, and song/album resolution. The only mild overlap is find_product vs resolve_music, since find_product can answer in resolve_music's shape, but the descriptions frame it as the category-uncertain entry point clearly enough.
Naming Consistency4/5
All tools use snake_case verb_noun names, which is consistent and predictable. The verbs vary (discover, find, resolve) and resolve_artist is more about discography than purchase links, but the pattern is still readable and disambiguating.
Tool Count5/5
Five tools is well-scoped for a product-link discovery service: one browse entry, one router, two live lookups, and one explicit not-live placeholder. Each tool earns its place and there is no filler.
Completeness4/5
The live music surface covers discovery, specific resolution, artist discography, and ambiguous-query routing, covering the core user workflows. Games are represented but intentionally not live, so that portion is a placeholder rather than a true dead end; a more complete set would include live game resolution.
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.
ParametersJSON Schema
| 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; 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
ParametersJSON 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
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint and openWorldHint annotations, the description discloses important behaviors: charts update weekly, links are verified at resolved_at, RootVine never fabricates data, and there are regional/scope limits. It also instructs on how to handle partial and no_results responses, giving the agent practical behavioral guidance.
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 dense but well-structured, starting with the overall purpose, then usage patterns, then caveats and error handling. Some phrasing is compressed and slightly run-on, but each sentence contributes meaningful information without redundancy.
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?
For a 5-parameter tool with no required parameters and an output schema, the description covers the main invocation modes, the relationship to resolve_music, limits, and error-handling expectations. An agent has enough context to call the tool correctly in most browsing and historical-chart scenarios.
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 useful semantics beyond the schema: 'position 1 is number one', 'No arguments gives the chambers and featured walls', and that each wall entry contains a query for resolve_music. It reinforces priority relationships already in the schema but adds the positional meaning and cross-tool handoff.
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 opens with a specific verb and resource: 'Browse live charts, genre and mood walls, editorial playlists, artist spotlights, and chart snapshots back to 1946.' It clearly differentiates this discovery-oriented tool from siblings like resolve_music by stating that wall entries contain a 'query for resolve_music'.
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 explicit usage patterns: no arguments for overview, 'year' for historical snapshots, 'wall' for entries, and 'resolve: true' for fetching links. It implies when to use resolve_music for individual lookups but does not explicitly state 'use resolve_music when you already have a query', leaving a small inference gap.
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.
ParametersJSON Schema
| 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
ParametersJSON 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
A4.6/5.0
Behavior5/5
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.
Conciseness4/5
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.
Completeness5/5
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.
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 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.
Purpose5/5
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.
Usage Guidelines4/5
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.
ParametersJSON Schema
| 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
ParametersJSON 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
A4.4/5.0
Behavior5/5
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.
Conciseness4/5
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.
Completeness5/5
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.
Parameters3/5
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.
Purpose5/5
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.
Usage Guidelines4/5
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.
ParametersJSON Schema
| 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
ParametersJSON 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
A4.6/5.0
Behavior5/5
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.
Conciseness4/5
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.
Completeness5/5
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.
Parameters3/5
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.
Purpose5/5
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.
Usage Guidelines5/5
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.
ParametersJSON Schema
| 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
ParametersJSON 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
A4.7/5.0
Behavior5/5
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.
Conciseness5/5
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.
Completeness5/5
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.
Parameters4/5
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.
Purpose5/5
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.
Usage Guidelines4/5
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
- 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; 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" + }, + "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" + ], + "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" + }, + "slug": { + "type": "string" + } + }, + "required": [ + "slug", + "name", + "description", + "entity_type", + "attribution", + "page_url" + ], + "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" +}
5 tool updates
- First observed
discover_music - First observed
find_product - First observed
resolve_artist - First observed
resolve_game - First observed
resolve_music
Related MCP Connectors
Neutral verified-merchant index for AI shopping agents; regulated/alcohol-first; earned-trust only.
Commission infrastructure for AI commerce — program discovery, attribution, and settlement.
Complete financial infrastructure for AI agents — payments, lending, escrow & more.
The independent agent-commerce protocol for AI-agent checkout on any online store.
Related MCP Servers
- MIT
Nexbidofficial
AlicenseNot gradedqualityCmaintenanceAgentic commerce infrastructure for AI agents. MCP-native product discovery, contextual ad matching, and purchase facilitation with European privacy compliance (nDSG/GDPR).MIT- AlicenseBqualityAmaintenanceAgent trust checks, reputation and signed passports. Glama's build is a separate local Guild with an empty graph and its own issuer. Registrations and evidence stay local. Use the remote MCP connector for the shared hosted Guild; its free preflight and metered trust services are separate.43Apache 2.0
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.