Skip to main content
Glama
Sign In

LLMExpert: cited Q&A over YouTube videos

by io.llmexpert
OverviewDiscussionsAdmin

Quote an ingest

quote
Read-only

Free. Expand YouTube URLs exactly as an ingest would and return the price, the per-video lines and the per-source rejections. Maps to POST /v1/quote. $0.01/min standard, $0.03/min whisper by default, 1-minute minimum per video. The quote_id is valid for 15 minutes; pass it to transcribe or add_sources to be charged exactly this price. Pass collection_id to price against an existing collection (videos already in it are free). At least one of url, urls, channel_url, channel_urls. Requires the key's read scope. Prices are the service defaults; quote returns the exact price.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOne YouTube URL (video, @handle, /channel/UC…, or playlist).
urlsNoSeveral YouTube URLs.
qualityNoTranscription quality (default standard).
languageNoOptional BCP-47 hint for transcription, e.g. en.
channel_urlNo`https://www.youtube.com/@handle`, `/channel/UC…`, or a playlist URL.
channel_urlsNoSeveral channel or playlist URLs.
collection_idNoPrice against this collection (videos already in it are free).
exclude_shortsNoSkip videos of 3 minutes or less when expanding a channel or playlist (default true); explicit video URLs are never skipped.
min_duration_secondsNoSkip expanded videos shorter than this many seconds.
max_videos_per_channelNoNewest-first cap on eligible videos per channel or playlist (default 25); Shorts and videos below min_duration_seconds are skipped before the cap.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / exclude_shorts
      Added value: +{
+  "description": "Skip videos of 3 minutes or less when expanding a channel or playlist (default true); explicit video URLs are never skipped.",
+  "type": "boolean"
+}
    • changedInput schema / properties / max_videos_per_channel / description
      Previous value: -"Newest-first cap applied to each channel or playlist (default 25)."New value: +"Newest-first cap on eligible videos per channel or playlist (default 25); Shorts and videos below min_duration_seconds are skipped before the cap."
    • addedInput schema / properties / min_duration_seconds
      Added value: +{
+  "description": "Skip expanded videos shorter than this many seconds.",
+  "maximum": 14400,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/openWorldHint; the description adds substantial behavior beyond them: the call is free, pricing rates ($0.01/min standard, $0.03/min whisper), a 1-minute per-video minimum, the 15-minute quote_id validity, and the required `read` scope. It also clarifies that collection videos already present are free and that returned prices are exact service defaults.

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?

Purpose and the free/price hook are front-loaded, and each following sentence carries operational detail. There is mild redundancy between the opening 'Free' and the pricing sentence plus the closing 'Prices are the service defaults; quote returns the exact price', which could be tightened.

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

Completeness5/5

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

For a 10-parameter, no-output-schema tool this covers what an agent needs: what it returns, that it costs nothing now, how the quote_id is consumed downstream, auth scope, and the mutual input constraint. Nothing material is left for the agent to infer before invoking it.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description still adds meaning the schema lacks, notably the cross-field constraint that at least one of url, urls, channel_url, or channel_urls must be supplied (required is 0 in the schema) and how collection_id affects pricing. It does not restate the expansion defaults (exclude_shorts, max_videos_per_channel), which the schema already covers.

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 gives a precise verb+resource (expand YouTube URLs exactly as an ingest would) and enumerates the return shape (price, per-video lines, per-source rejections), plus the backing endpoint POST /v1/quote. It is clearly separable from siblings like transcribe/add_sources because it is explicitly free and non-charging.

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?

It names the downstream alternatives (transcribe, add_sources) and the exact workflow: hold the quote_id for 15 minutes and pass it to be charged this price. It also states the at-least-one-of input requirement and the collection_id pricing option. It stops short of an explicit 'do not use this when you already have a quote / when you intend to charge immediately' exclusion, so it is clear context rather than full when/when-not guidance.

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

All LLMExpert: cited Q&A over YouTube videos 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