vimeo-mcp

Delete a folder

delete_folder

Destructive

Delete a Vimeo folder while keeping its videos in the main library by default; set delete_videos_too to permanently remove all videos too.

Instructions

Delete a folder. By default the videos inside it survive and return to the main library. Needs the delete scope. 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": {
      "folder_id": "<folder_id>"
    },
    "name": "delete_folder"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Set true only when the user asked for exactly this action.
`folder_id`	Yes	Folder id.
`delete_videos_too`	No	Also permanently delete every video in the folder. Off by default. This cannot be undone.

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: -"Deleting a folder cannot be undone. 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

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds non-obvious behavior: the default is non-destructive for contained videos (they return to the main library), the delete scope is required, and confirmation is mandatory. That materially improves an agent's ability to act safely. Minor gap: it doesn't describe what happens to empty folders or nested folders.

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?

Three short, front-loaded sentences with essentially no filler; the destructive-default caveat comes early. The opening clause duplicates the title verbatim, which is a small redundancy.

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 3-parameter mutation tool with no output schema, the definition covers scope, confirmation, and the key default behavior, which is enough to call it correctly. It omits edge cases such as nested folders or behavior when the folder is empty/already deleted.

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%, so baseline is 3, but the description adds meaning by explaining the default outcome of delete_videos_too (videos survive and return to the main library) and the hard requirement of confirm: true. These are outcome semantics beyond the schema's terse field text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Delete a folder') and immediately adds the consequential scope detail that contained videos survive by default, which is the key differentiator from delete_video. It does not explicitly name a sibling to contrast with, so it stops short of a 5.

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?

Gives prerequisites ('Needs the delete scope. Requires confirm: true.') which is real context, but says nothing about when to choose this over delete_video or remove_videos_from_folder, nor any when-not guidance. Usage is implied rather than framed.

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