Skip to main content
Glama

Ask a question about a YouTube video

ask_youtube_video
Read-only

Answers a question about a YouTube video using its transcript, citing the timestamp [mm:ss] where each point is made. Works for talks, lectures, tutorials, podcasts and webinars. If no question is given it returns the key takeaways.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe YouTube video link.
questionNoWhat to find out from the video. Optional; defaults to the key takeaways.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly=true, openWorld=true and destructive=false, so the safety profile is covered. The description adds genuine behaviour beyond that: the data source is the transcript, the response includes [mm:ss] citations per point, and omitting the question yields key takeaways. It does not mention failure modes such as missing/disabled transcripts, which is the main remaining gap.

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?

Three short sentences: purpose and mechanism first, then scope, then default behaviour. Nothing is repeated and nothing is padded; the reader gets the core facts in the first clause.

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 two-parameter, read-only tool with no output schema, the definition covers what it does, the data source, the citation format of the return value, and the default branch. Only edge-case behaviour (unavailable transcript, non-YouTube URLs, very long videos) is left unspecified.

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 both parameters ('url' and 'question') are already documented in the input schema. The description's note that a missing question defaults to key takeaways mirrors the schema's own default wording rather than adding new meaning, so the baseline of 3 applies.

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 states a specific verb and resource ('Answers a question about a YouTube video') plus the mechanism ('using its transcript') and the output shape ('citing the timestamp [mm:ss]'). An agent knows exactly what the tool produces without opening the schema.

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 gives clear scope ('Works for talks, lectures, tutorials, podcasts and webinars') and defines the no-question path ('returns the key takeaways'), which is useful routing context. It doesn't state exclusions or prerequisites (e.g. transcript unavailable, private videos), but with no siblings there is no alternative to route away from.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources