Skip to main content
Glama

batch_transcripts

Fetch transcripts for up to eight YouTube videos in one call, merging each into 30-second blocks with a character cap for quick comparison and analysis.

Instructions

Transcripts of several videos in one call (max 8), each merged into 30s blocks and capped.

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": {
      "urls": "<urls>"
    },
    "name": "batch_transcripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoauto
urlsYes
max_chars_eachNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavioral traits: a batch ceiling of 8, per-video merging into 30-second blocks, and output capping. It says nothing about authentication, rate limits, or partial failure (e.g., whether one bad URL fails the whole batch), which matters a lot for a fan-out tool.

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 dense sentence that front-loads the payload: what it returns, the batch limit, and the sharing behavior. No filler, though 'capped' is terse to the point of ambiguity given it overlaps with an actual parameter name.

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?

An output schema exists, so return values need not be described. However, for a three-parameter batch tool at 0% schema coverage, the description leaves the language selection and per-item truncation semantics unexplained, and omits batch failure behavior entirely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and largely fails to. 'Capped' loosely gestures at max_chars_each, and 'several videos' maps to urls, but the `lang` parameter is never explained and there are no format or constraint details for any of the three 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?

The description names a specific resource and scope: transcripts for 'several videos in one call', with a hard batch cap of 8. Saying 'several videos in one call' implicitly separates it from a single-video transcript tool, 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 only implied by 'in one call' and the max-8 limit, which suggests batching over repeated single calls. There is no explicit when-to-use versus when-not guidance, no mention of cost/latency tradeoffs, and no statement about what happens with more than 8 URLs.

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