Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_get_playlists

Read-only

List playlists from a connected Spotify or Apple Music account to import songs, with optional name filtering and paging. Requires the streaming source to be connected first.

Instructions

List your playlists from a connected streaming service (Spotify or Apple Music) so you can import songs from them. Requires that source to be connected (see vibo_get_me).

Input Schema

NameRequiredDescriptionDefault
qNoFilter playlists by name.
skipNoNumber of items to skip, for paging (default 0).
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns Vibo's payload untouched. No field projection: this server has no verified record of which Vibo fields matter, and inventing one would risk dropping a field a caller needs.
limitNoMax items to return (default 20).
sourceYesStreaming source — must be connected to your Vibo account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.5
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Vibo's payload untouched. No field projection: this server has no verified record of which Vibo fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the non-obvious precondition that the streaming source must be connected and points to vibo_get_me to verify it, which is real behavioral value beyond the annotations. It does not discuss paging or return shape, but the schema handles those and it neither repeats nor 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?

Two sentences, no filler, with the purpose front-loaded and the prerequisite immediately after. Every clause earns its place and nothing is repeated from the structured fields.

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 read-only listing tool with full annotation coverage and a fully documented 5-parameter schema, the description supplies what the structured fields cannot: the purpose and the connection precondition. The lack of any note about pagination defaults or result shape is minor since the schema's skip/limit/view entries cover those.

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 documents q, skip, view, limit, and source in detail; baseline is 3. The description only echoes the source concept (Spotify/Apple Music and the connection requirement) and adds no syntax or format detail beyond what the schema supplies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("List your playlists") and narrows the domain to a connected streaming source (Spotify or Apple Music), so it is not a tautology. It implies the downstream use (importing songs) which separates it from vibo_get_playlist_songs, but it never explicitly contrasts itself with that sibling, which would have earned a 5.

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 states a concrete prerequisite and a routing pointer: the source must be connected and the caller is told to check vibo_get_me. The intent (list playlists so you can import songs from them) gives usable context. It stops short of explicit when-not guidance or naming the alternative tools (vibo_get_playlist_songs, vibo_import_playlist_to_section).

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