Skip to main content
Glama
Sign In

Toolcall

by click.toolcall
OverviewDiscussionsAdmin

youtube-transcript

Full plain-text transcript of a YouTube video, de-duplicated and cleaned from the captions. Accepts a video id or URL. Ideal for feeding video content to LLMs. JSON response. [Paid: $0.01 USDC per call via x402 on Base; the calling client pays automatically.]

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": {
      "v": "<v>"
    },
    "name": "youtube-transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
vYesYouTube video id or full URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description partially carries the burden: it discloses deduplication, cleaning, JSON response, and payment cost ($0.01 USDC per call). However, it omits error handling, rate limits, or what happens if captions are unavailable.

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?

The description is concise: two main sentences plus a brief payment note. It is front-loaded with the core purpose and avoids redundancy, though the payment info could be integrated more smoothly.

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?

For a simple tool with one parameter and no output schema, the description covers purpose, input format, output format (JSON), and cost. It lacks error scenarios but is sufficient for typical 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 description coverage is 100%, and the description merely repeats the schema's parameter note ('Accepts a video id or URL'), adding no additional semantic value.

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 specifies the tool's function: extracting a full plain-text transcript from YouTube videos, with details on deduplication and cleaning. It uniquely distinguishes itself from sibling tools like 'pdf-extract' or 'reader' by targeting video content.

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?

The description suggests use for feeding video content to LLMs, providing a clear context. However, it does not explicitly state when not to use this tool or mention alternatives among siblings.

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

All Toolcall toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources