Skip to main content
Glama

Get transcript around a timestamp

get_passage
Read-onlyIdempotent

The transcript window around a moment in an item — use after search to read the full context of a hit (e.g. 90 seconds before and after). Free. For a summary or key points of one specific YouTube video, call show_player first with a short summary and the key points as moments, then write your answer citing timestamps.

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": {
      "at_seconds": "<at_seconds>"
    },
    "name": "get_passage"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoItem id from search/discover/list_episodes, e.g. "yt:dQw4w9WgXcQ"
urlNoAlternatively, a YouTube or podcast episode URL
at_secondsYesCenter of the window
after_secondsNo
before_secondsNo

Output Schema

NameRequiredDescriptionDefault
itemYesA piece of media. Pass `id` to get_transcript, get_passage or ingest.
segmentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a cost signal ("Free") and implies the output is transcript context around a hit, but says nothing about missing transcripts, clamping of the window, or error behavior. Adding the zero-cost note is real value, but the disclosure is thin beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded and does the real work. The trailing sentence about summaries and show_player is a different tool's workflow pasted in, making the description longer than its subject and diluting the primary instruction.

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?

An output schema exists, so return values need no explanation, and the core windowing use case is covered. Gaps remain on id-vs-url precedence, whether a window beyond transcript bounds is clamped, and what happens when no transcript exists — meaningful for a tool whose whole job is a bounded slice.

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 coverage is 60%: id, url and at_seconds are documented in the schema, while after_seconds and before_seconds carry only type/default/min/max with no descriptions. The phrase "90 seconds before and after" gestures at window sizing but never names those parameters and conflicts with the schema defaults (120 after, 60 before), so it adds only marginal meaning and mild ambiguity.

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?

Names a specific verb and resource ("transcript window around a moment in an item") and scopes it to a timestamp-centered slice, which distinguishes it from a full-transcript sibling in spirit. It stops short of naming get_transcript or search explicitly as the contrast, so an agent must infer that boundary.

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?

Explicitly says "use after search to read the full context of a hit," which gives a concrete when-to-use trigger and workflow position. It also offers an alternative path (show_player for summaries/key points), though that guidance is framed for the other tool rather than stating when NOT to call this one.

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