Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_get_section_songs

Read-only

Retrieve song requests for an event section with requester details, like counts, must-play/do-not-play flags, comments, and streaming links. Filter by text, flags, 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

TableJSON 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

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, so the safe read-only nature is covered. The description adds useful behavioral context beyond the annotations: it names the response fields a caller should expect and the supported sort dimensions. It does not discuss pagination or response shape nuances, but for a read-only list operation the description gives more than the structured annotations alone.

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, front-loaded with the main action and resource, followed by the key sorting capability. Every clause earns its place: the field list tells the caller what the response contains, and the sort mention aligns with the sortField parameter. No filler or redundancy with the parameter schema.

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?

Given a 10-parameter tool with no output schema, the description compensates by summarizing the main response content and sort behavior. Required parameters eventId and sectionId are documented in the schema, and the sectionId description even points to vibo_list_sections. A short mention of default pagination or the 'view' parameter would be marginally helpful, but the schema already covers those details.

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 70%, so the schema already documents most parameters including q, skip, limit, view, and filtering by flags. The description adds no new parameter-level meaning beyond mentioning the sort fields, which simply echoes the sortField enum already present in the schema. This meets the baseline for schema-covered parameters but does not exceed it.

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 clear action ('List') and a specific resource ('songs requested in a section'), and it goes beyond a bare name by enumerating the returned fields: who added each, like counts, must-play / do-not-play flags, comments, and streaming links. It also narrows the scope enough to distinguish it from sibling list tools like vibo_list_section_song_ideas or 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 Guidelines3/5

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

The usage is implied: if you need songs in a section, this is the tool that lists them. However, it gives no explicit guidance on when to prefer an alternative such as vibo_list_section_song_ideas or when a filter like vibo_search_songs would be more appropriate. The sort options are stated, but alternatives and exclusions are not.

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