Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Vimeo video captions

vimeo_video_captions_get
Read-onlyIdempotent

Retrieve a Vimeo video's caption and subtitle tracks, parsed WebVTT cues, and public metadata by video ID to support caption extraction and accessibility workflows.

Instructions

Get a Vimeo video's caption and subtitle tracks, their parsed WebVTT cues and the player's public metadata. Requires videoId.

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": {
      "videoId": "<videoId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "vimeo_video_captions_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
videoIdYesRequired. Vimeo video id, e.g. `76979871`.
languageNoOnly return tracks in this language, e.g. `en` or `en-x-autogen`. Matching is case-insensitive, and `en` also matches `en-x-autogen`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description contributes the return contents (caption tracks, parsed cues, public metadata), which is useful, but says nothing about pagination, size limits, behavior when no tracks exist, or the conversation_id handshake it requires.

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?

A single front-loaded sentence describing the resource and payload, with the requirement appended. The 'Requires `videoId`' clause mildly duplicates the schema's required array but costs little.

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 read-only, open-world fetch tool with no output schema, the description conveys enough about what comes back to set expectations. The unmentioned parts (conversation_id sequencing, empty-track behavior) are documented in the schema and needed only at call time.

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%, so every parameter is already documented, including the language matching rule and the analytics/context plumbing. The description only restates the videoId requirement, so the baseline 3 is appropriate.

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 a Vimeo video's caption and subtitle tracks') and even enumerates the payload: parsed WebVTT cues plus the player's public metadata. That distinguishes it from vimeo_video_get or transcript siblings by content, though no sibling is named explicitly.

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 implied by the content description — an agent can infer this is the tool for caption/subtitle retrieval — but there is no explicit when-to-use versus when-not guidance and no mention of the transcript-style alternatives that could also serve similar requests.

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

Deploy Server

Other Tools