vimeo-mcp

List texttracks

list_texttracks

Read-onlyIdempotent

List caption and subtitle tracks for a Vimeo video by ID, showing languages and the active track.

Instructions

List the caption and subtitle tracks on a video, with their languages and which one is active.

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

Input Schema

Name	Required	Description	Default
`video_id`	Yes	Video 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.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds useful context about the content returned ('with their languages and which one is active'), but omits pagination behavior, ordering, 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?

A single front-loaded sentence that states the resource and the key returned fields with zero waste. It is appropriately sized for a simple list tool with one parameter.

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 one-parameter read-only list tool with no output schema and annotations covering safety, the description is nearly complete: it identifies what is returned (languages, active track). It could still mention pagination or empty-result behavior, but no critical detail for correct invocation is missing.

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 there is only one parameter, so the schema already fully documents video_id. The description does not add syntax or constraints beyond noting the tracks belong to a video, which is the expected baseline when the schema does the heavy lifting.

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 clear verb+resource ('List the caption and subtitle tracks on a video') and specifies the scope. It distinguishes itself from mutation siblings like upload_texttrack/update_texttrack/delete_texttrack by its read-only listing action, but it does not explicitly name alternatives such as get_transcript or list_chapters.

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?

The description only says what the tool does, with no explicit when-to-use guidance, prerequisites, or named alternatives. The intended usage is implied by the purpose, but there is no routing information to help an agent choose this over get_transcript or list_chapters.

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