Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_get_section_songs

Read-only

Retrieve songs requested in a specific event section with requester, like counts, must-play or do-not-play flags, comments, and streaming links. Filter by text and sort by likes, date, or title.

Instructions

List the songs requested in a section, with who added each, like counts, must-play / do-not-play flags, comments, and streaming links. Sort by likesCount, createdAt, or title.

Input Schema

NameRequiredDescriptionDefault
qNoFilter songs by text.
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).
eventIdYesEvent id.
isFlaggedNoFilter to do-not-play / flagged songs.
sectionIdYesSection id (from vibo_list_sections).
sortFieldNo
isMustPlayNo
sortDirectionNo

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

A3.7/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 safety is covered; the description adds real value by disclosing the return shape (adder, like counts, must-play/do-not-play flags, comments, streaming links), which matters because there is no output schema. It stops short of describing ordering guarantees, pagination behavior, or size limits beyond what the schema states.

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?

Two tight sentences, front-loaded with what is listed before the sorting tail. The sorting sentence partially restates the sortField enum, but it is short and earns its place by telling the agent how ordering works.

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 10-parameter read tool with no output schema, the description covers the important gaps: what the records contain and how they can be ordered. Filtering and paging are left to the schema, which documents them adequately, so an agent can call this 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 ~70%, so the baseline is 3. The description does add meaning to sortField by spelling out the three sort keys, but it does not explain the filters (q, isFlagged, isMustPlay) or sortDirection, leaving a few parameters to schema text alone.

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?

States a specific verb and resource ("List the songs requested in a section") and enumerates the payload an agent gets back (who added each, like counts, flags, comments, streaming links). This clearly separates it from siblings like vibo_list_song_ideas_songs or vibo_get_playlist_songs, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the verb+scope: read the songs in a given section. However there is no when-to-use/when-not guidance, no mention of prerequisites beyond the schema's hint that sectionId comes from vibo_list_sections, and no routing away from the idea/playlist list tools.

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