Skip to main content
Glama
Sign In
OmniContext

OmniContext

by h4sht
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Save YouTube transcript to a file

youtube_save_transcript

Export a YouTube video's transcript to a local .md or .txt file for offline reading.

Instructions

Fetches a YouTube video's transcript and writes it to a local .md or .txt file, returning the file path. Use this when the user wants the full transcript exported for later reading, rather than reproduced in the chat.

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": {
      "url": "<url>"
    },
    "name": "youtube_save_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA YouTube video URL (e.g. https://youtube.com/watch?v=..., https://youtu.be/..., or a Shorts link) or an 11-character video ID.
langNoOptional ISO language code for the transcript (e.g. 'en', 'es'). Defaults to the video's default caption track.
destinationNoOptional file path or filename (.md or .txt) for the saved transcript. If it's a plain filename or omitted, the file is saved in the user's Downloads folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses writing to a local file and returning the path, but does not mention potential failures (e.g., unavailable transcript) or network behavior. Adequate for basic understanding.

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?

Two sentences, zero redundancy, front-loaded with purpose and usage context. Every word earns its place.

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?

Tool is simple with few parameters and no output schema. Description covers purpose, usage, and result adequately. Missing error/edge-case info but not critical for basic use.

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 coverage is 100%, so baseline is 3. The description adds file extension hints (.md/.txt) but no further parameter details. Schema already handles parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (fetches transcript and writes to file), the resource (YouTube video), and the result (file path). It distinguishes from the sibling youtube_get_transcript by noting the export for later reading rather than chat reproduction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool ('when the user wants the full transcript exported for later reading'), which contrasts with the implied sibling for chat output. Does not name the sibling explicitly but provides clear context.

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