Skip to main content
Glama

Get YouTube video detail

get_video
Read-onlyIdempotent

Video detail, thumbnail and citation link; says how the transcript was produced when recorded. Transcript is opt-in, bounded and pageable.

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": {
      "id": "<id>"
    },
    "name": "get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesVideo id from search_videos, e.g. 39218, or video:39218
include_similarNoAdd up to 5 similar records, each explained
transcript_offsetNoStart offset into the transcript (chars), with include_transcript
include_transcriptNoDefault false — set true to include the transcript text
transcript_max_charsNoMax transcript characters to return (default/max 25000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / include_similar
      Added value: +{
      +  "description": "Add up to 5 similar records, each explained",
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / transcript_max_chars / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / transcript_offset / maximum
      Removed value: -9007199254740991
  3. Changed3 schema fields changed
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "maxLength": 1000,
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / id / description
      Previous value: -"Video id from search_videos, e.g. 39218"New value: +"Video id from search_videos, e.g. 39218, or video:39218"
    • removedInput schema / properties / id / type
      Removed value: -[
      -  "string",
      -  "number"
      -]
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds one genuinely new behavior — that the response explains how a recorded transcript was produced — plus the fact that transcript retrieval is gated, capped, and pageable, though those facts largely restate schema constraints.

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-loading the payoff (detail, thumbnail, citation link) before the transcript caveats, with no filler. The telegraphic, verbless phrasing ('Video detail, thumbnail and citation link') is slightly awkward but costs little.

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

Completeness3/5

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

For a 5-parameter read tool with full schema coverage and no output schema, the description should sketch the return shape more fully; it names a few fields but never explains include_similar's behavior or what 'detail' comprises. It is adequate but leaves an agent guessing about response contents.

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 every parameter is already documented in the schema, including id formats, transcript offset, and max chars. The description's 'opt-in, bounded and pageable' phrasing reinforces those parameters conceptually but adds no syntax or edge-case meaning beyond them; baseline 3 applies.

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 the resource (video) and its payload (detail, thumbnail, citation link) plus the optional transcript, so an agent knows this fetches a single video's record. It lacks a verb ('Retrieve...') and never distinguishes itself from siblings like get_podcast or search, which keeps it below a 5.

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 statement of when to call this versus get_podcast, get_similar_items, or a search tool, and no prerequisites are given. The only usage-flavored content is that the transcript is opt-in, which is a parameter default rather than tool-level guidance.

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.