vimeo-mcp

Delete a caption track from a video

delete_texttrack

Destructive

Remove a caption track from a Vimeo video when given its video ID, track ID, and explicit confirm: true.

Instructions

Delete a caption track from a video. Requires confirm: true.

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": {
      "video_id": "<video_id>",
      "track_id": "<track_id>"
    },
    "name": "delete_texttrack"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Set true only when the user asked for exactly this action.
`track_id`	Yes	Track id.
`video_id`	Yes	Video id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.0.0Oct 6, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / confirm / default
```
Removed value: -false
```

changedInput schema / properties / confirm / description

Previous value: -"Set true to proceed."New value: +"Set true only when the user asked for exactly this action."

First observedv1.0.1Sep 1, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description's only added behavior is the confirm requirement, which is essentially a restatement of the schema's confirm field and does not disclose irreversibility or what data is lost.

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 short sentences, zero filler, and the confirm prerequisite is front-loaded where an agent will see it before constructing the call. Nothing could be removed without losing information.

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 destructive tool with full schema coverage and annotations carrying the safety profile, the description is nearly sufficient; it flags the required confirmation gate. It stops short of stating that the deletion is permanent and what happens to affected transcripts, which would be a useful omission to close.

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 description coverage is 100%, so video_id, track_id and confirm are already documented in the input schema. The description contributes no additional syntax, format, or meaning beyond what the schema provides, so the baseline of 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?

States a specific verb (Delete) plus a precise resource (caption track from a video), which cleanly separates it from siblings like delete_video, delete_chapter, delete_comment, and update_texttrack/upload_texttrack. An agent can select it without opening any schema.

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 adds one concrete gating rule (requires confirm: true), which is real usage guidance, but it says nothing about when to prefer this over alternatives or when not to use it. Usage is largely implied by the tool name rather than stated.

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