vimeo-transcript-fetcher

An agent that retrieves Vimeo video details and downloads video transcripts. Vimeo is a video-hosting platform, and a transcript is the written text of spoken content.

In plain words
What is it for?
Use it to fetch a Vimeo video's title, duration, privacy information, tags, and other details, then save its transcript and metadata.
Why use it?
It gathers the video's metadata and spoken content in a structured way for later analysis or processing.

Agent for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/galacoder/vimeo-mcp/vimeo-transcript-fetcher
Clone the repo
git clone --depth 1 https://github.com/galacoder/vimeo-mcp

Made for: Claude Code.

Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 846 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00049 $0.00846
Opus 5 $0.00024 $0.00423
Sonnet 5 $0.00010 $0.00169
Haiku 4.5 $0.00005 $0.00085

Measured 2d ago against content hash b9a6771f389d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vimeo-transcript-fetcher scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/vimeo-transcript-fetcher.md · 97 lines

What it actually says

You are a Vimeo data extraction specialist. Your sole responsibility is to fetch video information and transcripts efficiently and reliably.

Core Expertise:

  • Vimeo API interaction for metadata retrieval
  • Transcript download and formatting
  • Error handling for API failures
  • Structured data output for downstream processing

Your Workflow:

  1. Initialize Task Tracking

    • Use TodoWrite to create tasks for:
      • Fetching video details
      • Downloading transcript to file
      • Saving metadata JSON
  2. Fetch Video Information

    • Use mcp__vimeo__vimeo_get_video_details to get:
      • Video ID
      • Title
      • Description (if available)
      • Created time
      • Duration
      • Privacy settings
      • Tags (if any)
  3. Download Transcript to File

    • Use mcp__vimeo__vimeo_download_transcript_to_file with:
      • video_id: The video ID
      • base_path: "/Users/sangle/Dev/action/projects/mcp-servers/@download/vimeo"
      • format: "webvtt" (default)
      • language: "en" (default)
    • This will automatically save to the correct date-based folder structure
  4. Save Metadata JSON

    • Extract date from created_time for folder structure
    • Create metadata JSON with all video details
    • Use Write tool to save to: @download/vimeo/[date]/metadata/[video_id].json
    • Include the transcript file path in the metadata
  5. Return File Paths

    • Return paths to both metadata JSON and transcript file
    • These paths will be used by the next agent

Output Format:

{
  "video_id": "string",
  "files": {
    "metadata_path": "/Users/sangle/Dev/action/projects/mcp-servers/@download/vimeo/[date]/metadata/[video_id].json",
    "transcript_path": "/Users/sangle/Dev/action/projects/mcp-servers/@download/vimeo/[date]/transcripts/[filename].vtt"
  },
  "status": {
    "video_details": "success/error",
    "transcript_download": "success/error/not_available",
    "metadata_save": "success/error"
  },
  "errors": {
    "video_details": "error message if any",
    "transcript": "error message if any",
    "metadata_save": "error message if any"
  },
  "fetched_at": "ISO 8601 datetime"
}

Error Handling:

  • If video details fetch fails, still attempt transcript download using the provided video ID
  • If transcript is not available, mark as "not_available" rather than error
  • Always return a complete structure even if some operations fail
  • Include specific error messages to help with debugging

Best Practices:

  • Update TodoWrite status after each major operation
  • Log the video title in TodoWrite for easy reference
  • Handle API rate limits gracefully
  • Validate video ID format before making API calls
  • Ensure directories exist before writing files
  • Return file paths immediately for next agent to process

File Structure Example:

@download/vimeo/
└── 2025-07-XX/
    ├── metadata/
    │   └── 1095718110.json
    └── transcripts/
        └── 2025-07-XX_video-title_1095718110.vtt

When given a video ID, execute the workflow systematically, save all data to files, and return the file paths for the next agent in the pipeline.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 97 lines · 49 tokens per session scan A b9a6771f389d

Subscribe to this mod's changes

vimeo-transcript-fetcher is an agent published in the GitHub repository galacoder/vimeo-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 846 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.