vimeo-mcp

Delete a showcase

delete_showcase

Destructive

Delete a Vimeo showcase while keeping its videos in your library. Removes the curated order and branding; requires delete scope and confirm: true.

Instructions

Delete a showcase. The videos in it are not deleted, they stay in your library, but the showcase's curated order and branding are gone. 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": {
      "showcase_id": "<showcase_id>"
    },
    "name": "delete_showcase"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Set true only when the user asked for exactly this action.
`showcase_id`	Yes	Showcase 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: -"Deleting a showcase 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

A4.2/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotency, but the description goes further by disclosing the blast radius (videos are preserved, curated order and branding are permanently lost) and the authorization requirement (delete scope). That is exactly the beyond-annotations context an agent needs before firing a destructive call.

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?

Three short sentences, front-loaded with the action, then the consequence, then the prerequisites. Every sentence carries distinct information and none repeats the schema or title verbatim.

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 destructive mutation with no output schema, the description covers what is destroyed, what is preserved, and the scope/confirm prerequisites. The only gap is that it never states outright whether the deletion is reversible or what error surfaces when confirm is omitted, though the annotations imply non-idempotency.

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 confirm with its 'only when the user asked for exactly this action' wording. The description's 'Requires confirm: true' restates rather than extends that semantics, so the baseline 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+resource ('Delete a showcase') and immediately disambiguates from the other delete_* siblings by naming the exact entity. It also scopes the operation by explaining that contained videos survive while the showcase's order and branding do not, so an agent knows precisely what is removed.

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?

It gives invocation preconditions ('Needs the delete scope', 'Requires confirm: true'), which is real usage guidance, but it never states when to prefer this over alternatives such as update_showcase or when deletion is inappropriate. Usage is implied rather than routed.

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