Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

youtube-subtitle-scraper

Scrape subtitles from a YouTube video by supplying its URL. Extract ready-to-use caption text for transcription, translation, or content analysis workflows.

Instructions

Scrape subtitles from a specified YouTube video. Important: a video URL is required.

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-subtitle-scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesVideo URL (retrieveable on desktop); must start with https://
env_idsNoOne or more environment IDs where this task should run. If the user did not provide environment details (name, id, remark, serial number), prompt for them or offer to help create an environment.
run_timeoutNoOverall process timeout in seconds. The environment will be closed automatically after this period.
is_cancel_closeNoShould the environment be closed after the execution is completed? 0 means close, 1 means do not close. The default is 0. If you set it to 1, please set run_timeout to 0 to avoid automatic closing due to timeout.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says nothing about how the scrape runs — the presence of env_ids and run_timeout implies a task dispatched into an environment, but the description never explains that, nor what happens on timeout, whether the environment is closed, or what form the subtitles come back in.

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?

Two short sentences, front-loaded with the verb and resource, with zero filler. It is concise but borders on under-specified; nothing is wasted, though little is offered.

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?

This is a four-parameter tool with an environment-dispatch model, a timeout, and a post-run close flag, plus no annotations and no output schema. The description never explains the environment concept, the timeout behavior, or what output an agent should expect, so it is incomplete for the tool's actual complexity.

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 the schema already documents url, env_ids, run_timeout, and is_cancel_close in detail. The description adds nothing beyond the schema — it only re-emphasizes that the URL is required — which lands at the baseline for fully documented parameters.

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+resource: 'Scrape subtitles from a specified YouTube video.' An agent can tell this apart from siblings like youtube-comments-scraper or youtube-like-comment-viewer by the resource named, though the description itself does not name any alternative.

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?

There is no when-to-use guidance, no preconditions, and no mention of when not to use this in favor of a sibling. The only guidance offered ('a video URL is required') restates the schema's required field rather than helping an agent choose this tool.

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