vimeo-mcp

Get showcase

get_showcase

Read-onlyIdempotent

Fetch a Vimeo showcase and its curated video list. Control whether videos are included and how many results to return per page.

Instructions

Get one showcase and the videos in it, in their curated order.

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

Input Schema

Name	Required	Description
`per_page`	No
`showcase_id`	Yes	Showcase (album) id.
`include_videos`	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.3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds one genuinely useful trait beyond the annotations: videos come back in their curated order, implying ordering is author-defined rather than by date. It says nothing about pagination even though per_page exists.

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?

A single short sentence with the resource and the return scope front-loaded. No padding or redundant restatement of the title.

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 read-only lookup with no output schema, the description usefully signals what comes back (the showcase plus its ordered videos). However, it omits pagination behavior for a tool that exposes per_page up to 100, leaving an agent unaware of result limits.

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 coverage is only 33%: showcase_id is documented in the schema, while per_page and include_videos are not described anywhere. The phrase 'and the videos in it' loosely hints at the include_videos toggle, but the pagination parameter is entirely unaddressed, so the description does not compensate for the coverage gap.

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 and resource (get one showcase) and adds scope (also returns the videos, in curated order), which separates it from list_showcases and get_video. It does not name an alternative, but the singular 'one showcase' is unambiguous.

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?

Usage is only implied: fetch a single showcase by id. There is no statement of when to prefer this over list_showcases or get_video, and no prerequisites or exclusions.

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