Skip to main content
Glama
Sign In
ParseJet - Universal File & URL Parser

ParseJet - Universal File & URL Parser

by yooumuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_youtube_transcript

Retrieve the transcript from a YouTube video using its URL. Optionally specify a language code for subtitles in a specific language.

Instructions

Get the transcript of a YouTube video, optionally in a specific language.

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

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video URL
languageNoISO 639-1 language code for the transcript (e.g. 'en', 'ja', 'zh')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits, but it only states 'Get the transcript' without mentioning side effects, error cases (e.g., missing transcript), or limitations (e.g., rate limits, language availability).

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?

The description is a single, concise sentence that is front-loaded and contains no extraneous information, earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description should provide more context about return values, error handling, or output format (e.g., segments with text and timestamps). The current one-liner is insufficient for a tool with two parameters.

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 the schema already documents parameters. The description adds minimal value by confirming 'language' is optional, but does not provide further semantic enrichment beyond the schema.

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 ('Get'), the resource ('transcript of a YouTube video'), and the optional language parameter, effectively distinguishing it from sibling tools like 'parse_file' and 'parse_url'.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites (e.g., video must have captions, no authentication requirements). The description lacks contextual usage direction.

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