Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_delete_section

Destructive

Delete a timeline section and all its songs, answers, and comments permanently. A preview names the section and its contents; do-not-play and headline sections need force:true to remove.

Instructions

Delete a timeline section, with every song, answer and comment in it — this cannot be undone. The preview names the section and how many songs and answered questions it holds. Sections of type "dontPlay" (the DJ's do-not-play list) and "headline" (timeline dividers) are refused unless force:true. 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
forceNoRequired to delete a "dontPlay" or "headline" section.
eventIdYesEvent id.
sectionIdYesSection _id from vibo_list_sections.
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. Addedv2.4.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the traits that matter: irreversible cascade to songs, answers and comments, the force bypass for protected section types, and the two-phase confirm/confirmToken flow. This is well beyond what the annotations supply.

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?

Four sentences, front-loaded with the irreversible consequence, then constraints, then confirmation mechanics. Dense but every sentence carries information; only the parenthetical glosses on section types could be trimmed.

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?

With no output schema, the description carries the return-value burden and does so: it describes the preview content (section name, song and answer counts) and the confirmToken response. An agent has everything needed to call it and to handle both confirmation paths.

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 coverage is 100% and already documents force, confirmToken and sectionId, so baseline is 3. The description adds the rationale for force (which section types are refused) and situates confirmToken inside the two-step flow, giving it meaning beyond the schema's field-level note.

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?

States a specific verb (delete) plus resource (timeline section) and the cascade scope (every song, answer and comment), which cleanly distinguishes it from vibo_delete_section_comment and vibo_update_section.

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

Usage Guidelines5/5

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

Explicitly states the precondition for refusal (dontPlay and headline sections need force:true) and the confirmation protocol, including what to do on a client without elicitation. The agent knows exactly when this call will fail and how to recover.

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