vimeo-mcp

Update a showcase's name, description, privacy or sort order

update_showcase

Idempotent

Modify a Vimeo showcase's name, description, privacy, or sort order by passing only the fields to change.

Instructions

Update a showcase's name, description, privacy or sort order. Only the fields you pass change.

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": "update_showcase"
  }
}

Input Schema

Name	Required	Description
`name`	No
`sort`	No
`privacy`	No
`password`	No
`description`	No
`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

B3.1/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds one genuinely useful behavioral fact beyond them: 'Only the fields you pass change', i.e. PATCH semantics. It omits, however, any mention of the password requirement when privacy is set to 'password' and says nothing about failure modes.

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, scope front-loaded, and the second sentence earns its place by establishing partial-update semantics. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter mutation with 17% schema coverage and no output schema, the description is minimally adequate: it covers the field list and partial-update behavior but leaves the password/privacy interaction and any error or permission context unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% — just showcase_id is documented — so the description must carry the load. It names name, description, privacy, and sort but silently omits the password parameter and gives no meaning for the two enums, leaving a functionally important parameter undocumented in both places.

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 ('Update') plus resource ('a showcase's') and enumerates the mutable fields, so an agent can separate it from update_video, update_folder, and update_chapter by resource alone. The title is an exact restatement, so the description adds no differentiation beyond the resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no reference to alternative tools such as update_video or update_folder for other resource types. The only usage-adjacent statement is the partial-update note, which is behavioral rather than routing.

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