vibo_delete_song_comment
Delete a comment on a song by providing its comment, song, section, and event IDs. Requires user confirmation, returning a preview and confirmToken for clients without elicitation support.
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).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"eventId": "<eventId>",
"sectionId": "<sectionId>",
"songId": "<songId>",
"commentId": "<commentId>"
},
"name": "vibo_delete_song_comment"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| songId | Yes | Song _id (from vibo_get_section_songs). | |
| eventId | Yes | Event id. | |
| commentId | Yes | Comment _id to delete. | |
| sectionId | Yes | Section id. | |
| confirmToken | No | 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. |