Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_import_playlist_to_section

Import selected Spotify/Apple Music tracks into an event section after user confirmation. Returns counts of added, existing, and ignored tracks to keep the playlist update transparent.

Instructions

Import selected tracks from a connected Spotify/Apple Music playlist into a section. Returns counts of added/existing/ignored. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesStreaming source — must be connected to your Vibo account.
eventIdYesEvent id.
sectionIdYesSection id (from vibo_list_sections).
playlistIdNoPlaylist id from vibo_get_playlists.
tracksToAddYesTrack ids (from vibo_get_playlist_songs) to import.
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
tracksToIgnoreNoTrack ids to skip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.1
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv1.5.3
  4. Removedv1.4.3
  5. First observedv1.3.1

TDQS

A4.7/5.0
Behavior5/5

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

Despite sparse annotations, the description discloses key behaviors: it is a mutating import that returns counts, requires user confirmation, and has a two-phase fallback where the first call returns a preview and confirmToken and only a repeat call with that token proceeds. This is substantial behavioral context beyond 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?

Two dense sentences: the first states the purpose and outcome, the second explains the confirmation behavior. No filler, and the most important information is front-loaded.

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 7-parameter import tool with no output schema, the description covers the return format, confirmation requirement, and fallback token mechanics. Combined with the rich per-parameter schema, an agent has enough to invoke the tool correctly.

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% and the property descriptions are already detailed, including the source enum, token constraints, and provenance from sibling tools. The description adds the phase-1/phase-2 confirmToken lifecycle and the connected-account prerequisite, but most parameter meaning is carried by the schema, so this is modest added value beyond the baseline.

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 and resource: 'Import selected tracks from a connected Spotify/Apple Music playlist into a section.' It also names the return value ('counts of added/existing/ignored'), which distinguishes this batch import from sibling single-song and export tools.

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

Usage Guidelines4/5

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

The description gives clear invocation context: source must be a connected Spotify/Apple Music playlist, and it explains the required confirmation flow ('Asks the user to confirm first'). It does not explicitly name alternatives such as vibo_add_song_to_section, so the 'when not to use' guidance is missing, but the context is otherwise unambiguous.

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

Deploy Server

Other Tools