Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_search_songs

Read-only

Search songs to add to an event section. Query as ' - ' to find official recordings and check each result's quality verdict before adding.

Instructions

Search for songs to add to a section. ALWAYS query as " - " with a space-hyphen-space separator (e.g. "Ed Sheeran - Thinking Out Loud"). Vibo's default 'searchField' index is a loose text match over a catalog full of YouTube covers, karaoke tracks and re-uploads: the hyphenated form resolves to the official recording, while the same words unhyphenated rank covers and re-uploads above it (measured live — "Chris Stapleton - Tennessee Whiskey" returned only the official master; without the hyphen, none of the nine results was the original). Each result carries a quality verdict (likely-original / uncertain / likely-not-original) plus warnings — check it before adding, and never add a likely-not-original result without saying so. source 'spotify' searches your connected Spotify (a structured catalog, so the hyphen matters less). Returns songUrl/viboSongId/title/artist for vibo_add_song_to_section.

Input Schema

NameRequiredDescriptionDefault
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 results (default 20).
queryYesSong to search for, as "<Artist> - <Title>" (space-hyphen-space). Use the artist's own stylization — the index does not fold variants together, and "Dan + Shay - Speechless" returns the official master while "Dan and Shay - Speechless" returns covers and live cuts without it. Artist alone returns only a short popularity-ranked subset of their catalog, so a specific track may be missing entirely. If the hyphenated query looks wrong, retry as "<Title> - <Artist>", then the title alone filtered by artist.
sourceNoSearch source (default 'searchField').
eventIdYesEvent id (search is scoped to an event/section).
sectionIdYesSection id the search is for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Changed1 schema field changedv1.8.0
    • 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"
+}
  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?

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered, yet the description adds substantive behavior beyond them: the loose text-match index behavior, the cover/karaoke/re-upload ranking quirk, the per-result quality verdict and warnings, and how the two sources differ. This is real disclosure an agent needs to interpret results correctly, not a restatement of structured fields.

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?

Front-loaded with the single most important instruction (the mandatory hyphenated query form) before any justification or edge cases. It runs long and the embedded measured-evidence parenthetical ('nine results was the original') is the least essential sentence, but every other clause maps to a decision the caller must make.

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?

With 6 parameters, two enums and no output schema, the description does the work of explaining what comes back (songUrl/viboSongId/title/artist plus the quality verdict) even though it does not enumerate every result field. It covers the scoping to event/section implicitly but never clarifies the `view` or `limit` behavior in prose, leaving a minor gap against the full search surface.

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 schema already documents the hyphen format, retry chain, and artist-alone limitation, so much of the parameter prose is duplicative. The description nonetheless adds meaning for `source` that the schema lacks — that 'spotify' hits a structured catalog where the hyphen matters less — which nudges it above the baseline 3.

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 and resource ('Search for songs') and a concrete intent ('to add to a section'), which distinguishes it from read-oriented siblings like vibo_get_section_songs. It even names the downstream sibling (vibo_add_song_to_section) that consumes its output, so the agent can place it in the workflow without opening either schema.

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?

Explicit when/when-not guidance: ALWAYS use the hyphenated '<Artist> - <Title>' form, choose source 'spotify' when searching a structured catalog, and check the quality verdict before adding. It also states a failure-mode exclusions rule — 'never add a likely-not-original result without saying so' — and gives a retry ordering, which is exactly the routing depth the top band requires.

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