Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_import_playlist_to_section

Import selected Spotify or Apple Music playlist tracks into a Vibo event section, with confirmation and added/existing/ignored counts.

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

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.3/5.0
Behavior5/5

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

Annotations only give the coarse profile (readOnly=false, destructive=false, openWorld=true); the description adds substantive behavior: the return counts of added/existing/ignored, and the non-obvious two-phase confirmation flow with confirmToken semantics (never on the first call, never invented, never reused, ignored under elicitation). That is exactly the kind of context structured fields cannot convey.

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?

Three sentences, front-loaded with purpose and return shape, then the confirmation rule. The third sentence is dense and nested but every clause carries operational information (client-dependent branch, preview/token mechanics), so little is wasted.

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

Completeness4/5

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

For a 7-parameter mutation with no output schema, the description covers purpose, return counts, and the tricky confirmation branch. It omits edge cases such as conflict between tracksToAdd and tracksToIgnore or failure behavior when the source is not connected, but nothing essential for a correct call is missing.

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 every parameter including the confirmToken protocol is already documented in the schema — the description largely restates it. It adds no extra meaning for tracksToAdd/tracksToIgnore interaction or the playlistId-vs-tracksToAdd relationship, so the baseline 3 applies.

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?

States a specific verb (import), a specific resource (tracks from a connected Spotify/Apple Music playlist), and a destination (a section). This clearly distinguishes it from the single-track sibling vibo_add_song_to_section and the read-only vibo_get_playlist_songs.

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?

Gives strong contextual guidance on the confirmation protocol — when the client supports a prompt versus when the two-step preview/confirmToken fallback applies — which is the main decision an agent must make. It does not, however, explicitly name alternatives (e.g., use vibo_add_song_to_section for a single track), so it stops short of full when-not guidance.

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