vimeo-mcp

Remove one video from a showcase

remove_video_from_showcase

Idempotent

Remove a video from a Vimeo showcase without deleting it from your library. Provide showcase_id and video_id to detach the video.

Instructions

Remove one video from a showcase. The video itself is untouched and stays in your library.

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": {
      "showcase_id": "<showcase_id>",
      "video_id": "<video_id>"
    },
    "name": "remove_video_from_showcase"
  }
}

Input Schema

Name	Required	Description	Default
`video_id`	Yes	Video id to remove.
`showcase_id`	Yes	Showcase id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 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
```
First observedv1.0.1Sep 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds meaningful non-destructive behavior: the video remains in the library, so removal only affects the showcase association.

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 sentences, front-loaded with the core action and immediately followed by the critical non-destructive clarification. No sentence is wasted.

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 two-parameter, idempotent, non-destructive mutation, the description plus annotations and full schema coverage give the agent enough to call it correctly. Missing only minor details such as error behavior if the video is not in the showcase.

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%, and the schema already documents both showcase_id and video_id. The description does not add syntax, format, or edge-case meaning beyond what the schema provides, so baseline 3 is appropriate.

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, resource, and scope: 'Remove one video from a showcase.' The clarification that the video itself is untouched distinguishes it from sibling tools like delete_video while directly mapping to the showcase context.

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?

Provides clear context: use this to detach a video from a showcase without deleting it. It does not explicitly name alternatives such as delete_video or remove_videos_from_folder, but the key distinction from deletion is stated.

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