Skip to main content
Glama

Show video player

show_player
Read-onlyIdempotent

Show your answer about one YouTube video as an interactive card: the video player, a one- or two-sentence summary, and your answer organized as sections (a short heading each, with points that each carry the seconds they come from; clicking a point plays that moment). Use it for any answer about one specific video (a summary, brief, key points, quotes, or a question about what it says). Call it BEFORE writing your reply: the card is the organized answer, so your reply should then be only a few sentences answering the question directly, without repeating the points. Check each point's seconds against the transcript first and call it once per answer: each call shows a separate card in the chat. It returns CleoLM links for each point (watch_url) for any timestamp you mention. moments (a flat list) is the older form. Free. YouTube only; not for podcasts.

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

Input Schema

NameRequiredDescriptionDefault
idNoItem id from search/discover/list_episodes, e.g. "yt:dQw4w9WgXcQ"
urlNoAlternatively, a YouTube or podcast episode URL
titleNoVideo title, if you already have it
channelNo
momentsNoOlder flat form of the key points, in any order; prefer sections
summaryNoOne or two sentences: what the video argues or covers
sectionsNoYour answer, organized: 3-6 sections for a summary, 1-2 for a specific question

Output Schema

NameRequiredDescriptionDefault
urlYes
titleNo
channelNo
item_idYes
momentsYes
summaryNo
sectionsNo
video_idYes
read_along_urlYesCleoLM page for this video, opening with this summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: it returns CleoLM `watch_url` links per point, it is free, and it is YouTube-only. The one tension is "each call shows a separate card in the chat," which implies a repeatable visible side effect against idempotentHint=true – mild, not a direct contradiction, since no data is mutated.

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?

Dense but front-loaded: the card's composition comes first, then the usage rule, then the reply protocol, then limitations. Nearly every clause carries new information; the "check each point's seconds against the transcript" instruction earns its place because it prevents wrong timestamps.

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 7-parameter, zero-required tool with nested sections, the description covers output shape, call timing, post-call reply style, and scope limits, while the schema handles the id/url/title fields. Minor gaps remain: it does not say what happens when no transcript exists or when the id/url cannot be resolved.

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 already 86%, so the baseline is 3; the description earns an increment by explaining the intended shape of `sections` ("3-6 sections for a summary, 1-2 for a specific question"), that each point carries its source seconds, and that `moments` is the older flat form to avoid.

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?

States a specific action and output: an interactive card containing the video player, a `summary`, and `sections` whose points play the referenced moment. It is immediately distinguishable from siblings like `get_transcript` or `search`, which retrieve content rather than render an answer card.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit about when to use ("any answer about one specific video... summary, brief, key points, quotes, or a question"), when not to ("YouTube only; not for podcasts"), and the sequencing rule ("Call it BEFORE writing your reply... your reply should then be only a few sentences"). It also states the call cardinality: once per answer, since each call shows a separate card.

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