Skip to main content
Glama

delete_chapter

Destructive

Remove a specific chapter marker from a Vimeo video without altering the video file. Requires explicit confirmation to proceed.

Instructions

Delete one chapter marker. The video is untouched. Requires confirm: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoSet true to proceed.
video_idYesVideo id.
chapter_idYesChapter id.
Install Server

TDQS

A4.2/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond annotations by stating 'Requires confirm: true' and clarifying that the video is untouched. This is useful because the annotations mark the operation as destructive and non-idempotent, but the description reassures that the destructive effect is limited to the chapter marker.

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 concise sentences with no filler. The core action is front-loaded, and the critical confirmation requirement is stated immediately after. Every sentence earns its place.

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?

For a simple deletion tool with two required ID parameters and a confirm flag, the description covers the essential behavioral requirements. No output schema exists, so return-value documentation is not expected. Irreversibility could be mentioned, but the destructive annotation and confirm requirement already convey this.

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 the parameters are already documented. The description adds value by explicitly noting that confirm must be set to true, reinforcing the schema's default of false. It does not add further detail on video_id or chapter_id, but the schema already provides adequate descriptions.

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: 'Delete one chapter marker.' It clearly distinguishes this from deleting videos, comments, or text tracks, and clarifies the video itself is untouched.

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?

The description communicates exactly when to use this tool: when deleting a single chapter marker. The 'video is untouched' note helps the agent understand scope. It does not explicitly name alternative tools, but no direct sibling alternative exists for deleting chapters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/navidmoazzez/vimeo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server