vimeo-mcp

Update a video's title, description or privacy

update_video

Idempotent

Modify a Vimeo video's title, description, or privacy settings; only supplied fields change, requiring edit scope.

Instructions

Update a video's title, description or privacy. Only the fields you pass change. Needs the edit scope.

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>"
    },
    "name": "update_video"
  }
}

Input Schema

Name	Required	Description
`name`	No	New title.
`password`	No	Required when privacy_view is 'password'.
`video_id`	Yes	Video id.
`description`	No	New description.
`privacy_view`	No	Who can watch. 'unlisted' gives a shareable link that is not listed publicly. 'disable' blocks playback on vimeo.com while leaving embeds working.
`privacy_embed`	No	Where it can be embedded. 'whitelist' restricts it to the domains you allow.

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/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true). The description adds two important non-annotation facts: partial-update behavior and the required OAuth scope. It does not describe the response shape or error conditions.

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 are front-loaded with purpose, then behavioral detail, then the auth requirement. Every sentence earns its place and there is no 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 six-parameter mutation tool with no output schema, the description covers purpose, partial-update semantics, and required auth scope, while annotations cover safety. It could mention what the call returns or side effects on embeds, but it is largely complete.

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 documents all six parameters including enum meanings. The description does not add syntax, format, or default-value details beyond what the schema already provides, so the baseline 3 applies.

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?

The description states a specific verb, resource, and field scope: 'Update a video's title, description or privacy.' This clearly distinguishes it from siblings like set_video_tags or set_video_thumbnail by the fields it updates, though it does not explicitly name any alternative tool.

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?

It provides a clear prerequisite ('Needs the edit scope') and partial-update semantics ('Only the fields you pass change'), which tell the agent when this tool is appropriate. It does not name alternative tools or state when not to use it, so it lacks explicit exclusions.

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