Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_reorder_songs

Reorder songs in a section by moving specified songs after a target song or to the top. Checks permissions and confirms before applying changes.

Instructions

Reorder songs within a section: move sourceSongIds (in the given order) to directly after targetSongId, or to the top when it is omitted. Checks the ids against the section and, for a host, that the DJ allows hosts to order this section's songs. That setting is OFF for every section a host creates and only the DJ can turn it on, so a host usually cannot reorder songs in sections they added. Sends one reorderSongsBatch call per song that actually moves. 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

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYesEvent id.
sectionIdYesSection id.
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.
targetSongIdNoplace the moved songs directly after this song _id; omit for the top
sourceSongIdsYesSong _ids from vibo_get_section_songs, in the order they should end up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.4.0
    • changedInput schema / properties / sourceSongIds / description
      Previous value: -"Song _ids from vibo_get_section_songs."New value: +"Song _ids from vibo_get_section_songs, in the order they should end up."
    • changedInput schema / properties / targetSongId / description
      Previous value: -"place the moved songs after this song _id; omit for start"New value: +"place the moved songs directly after this song _id; omit for the top"
  2. 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"
+}
  3. 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"
  4. Addedv1.5.3
  5. Removedv1.4.3
  6. First observedv1.3.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false), it discloses the permission model, the per-song reorderSongsBatch call behavior, and the full confirmation protocol including the preview/confirmToken two-step fallback and the MCP_CONFIRM_MODE reference. This is unusually rich behavioral disclosure for a mutation tool.

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?

The core action is front-loaded in the first clause, and subsequent sentences cover preconditions and the confirmation flow. It is dense but largely earns its length, with only minor overlap between the description's confirmToken explanation and the schema's own.

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

Completeness5/5

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

Given no output schema and a moderately complex mutation, the description covers preconditions, likely failure modes (host permission), server call behavior, and the confirmation/return flow (preview plus confirmToken). An agent has enough to invoke it correctly and route the confirmation.

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 100%, so all five parameters already have descriptions, including the omit-for-top behavior of targetSongId and the confirmToken protocol. The description reinforces ordering semantics ('in the given order') but adds little beyond what the schema already states, 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?

The description states a specific verb and resource ('Reorder songs within a section') and defines the exact operation: move sourceSongIds in order to directly after targetSongId, or to the top when omitted. This cleanly separates it from siblings like vibo_reorder_sections (sections, not songs) and vibo_move_song.

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 gives strong contextual guidance: ids are checked against the section, host reordering requires a DJ-enabled setting that is OFF by default, so hosts usually cannot reorder sections they created. It does not explicitly name an alternative sibling to use instead, but the when/when-not conditions are clear.

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