Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_delete_song_comment

Destructive

Delete a song comment after user confirmation. Requires event, section, song, and comment IDs.

Instructions

Delete a comment on a song. 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
songIdYesSong _id (from vibo_get_section_songs).
eventIdYesEvent id.
commentIdYesComment _id to delete.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  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/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, so the destructive nature is known. The description goes further by detailing the confirmation protocol: it explains the two modes (client-supported prompt vs. two-step fallback with confirmToken) and explicitly states that a repeat call is required with the token. This adds significant behavioral context beyond the annotations, clarifying the exact interaction flow and the token's role.

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?

The description is two sentences long, with the core purpose ('Delete a comment on a song') front-loaded. The confirmation behavior is explained concisely without extraneous detail. Every word contributes to understanding the tool's function and its special confirmation handling.

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 the destructive nature, the description covers the critical confirmation behavior comprehensively. All parameters are described in the schema, and the description explains the two-step flow when needed. There is no output schema, but the description doesn't need to explain return values since the confirmation flow itself is the main behavioral nuance. For an agent to call this correctly, it has all necessary information: required IDs, the confirmation process, and the token handling.

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 description coverage is 100%, so all parameters are already described in the schema. The description adds value by explaining the confirmation flow that directly relates to the confirmToken parameter, clarifying how and when it should be used. This goes beyond the schema's parameter-level descriptions, providing the overarching behavior that ties the parameters together.

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 the action 'Delete' and the resource 'a comment on a song', making the purpose unambiguous. It naturally distinguishes from the sibling vibo_delete_section_comment by specifying the song context. The verb-resource pair is specific and leaves no ambiguity about what the tool does.

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 description clearly implies the tool is for deleting song comments, but it does not explicitly mention alternatives or exclusion criteria. It also does not state prerequisites such as needing a comment ID from a prior call, though the schema covers that. The confirmation flow is described, which helps with when to call twice, but there is no explicit guidance on when not to use this tool versus other delete 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