vimeo-mcp

Create a showcase

create_showcase

Create a Vimeo showcase to group and order videos with configurable sort, privacy, and password settings.

Instructions

Create a showcase. Needs the create 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": {
      "name": "<name>"
    },
    "name": "create_showcase"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Showcase name.
`sort`	No	How videos are ordered. 'arranged' means your manual order.	arranged
`privacy`	No	Who can see the showcase page.	anybody
`password`	No	Required when privacy is 'password'.
`description`	No

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

Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), lowering the bar. The description adds the required create scope, which is exactly the kind of auth context the rubric credits, but it says nothing else about behavior (e.g., whether the new showcase starts empty or what is returned).

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?

Two short sentences with no wasted words and the purpose front-loaded before the prerequisite. It is efficient, though the brevity borders on under-specification rather than optimal conciseness.

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 5-parameter creation tool with no output schema, the description covers only purpose and auth scope. It omits what the caller gets back (e.g., the new showcase identifier) and any note about the created resource's initial state, leaving the definition minimally adequate.

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 80%, so the schema already documents name, sort, privacy, and password (including the conditional password requirement). The description adds no parameter meaning whatsoever, 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?

"Create a showcase" states a specific verb and resource, and the resource noun distinguishes it from siblings like create_folder and create_chapter. However, the sentence is a near-verbatim restatement of the tool title and adds no scoping detail beyond the name, so it does not reach the 5 tier.

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?

"Needs the create scope" gives an actionable prerequisite, which helps an agent confirm it can call the tool. There is no explicit when-to-use vs alternatives guidance (e.g., versus update_showcase), but the verb/resource pairing makes the intent inferable.

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