Skip to main content
Glama

Get transcript section

get_transcript_section
Read-only

Read only part of a transcript, between two timestamps, e.g. one chapter of a long podcast or the ten minutes around a moment found with find_in_transcript. Much smaller than the full transcript.

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": {
      "video": "<video>",
      "from": "<from>"
    },
    "name": "get_transcript_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd time in the same formats. Omit to read to the end.
fromYesStart time: "12:30", "1:02:00", or seconds like "750".
langNoOptional BCP-47 caption language code. Omit for the default track.
videoYesYouTube video URL or 11-character video ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description usefully adds the cost/size signal ('much smaller'), but says nothing about failure modes such as missing captions, out-of-range timestamps, or whether the returned text includes timestamps.

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?

Two short sentences, both front-loaded with the core scope first and the concrete examples second. No redundant restatement of the name or title, and every clause carries information.

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 simple read tool with full schema coverage and clear annotations, the definition supplies what an agent needs to select and invoke it. The remaining gap is output shape and edge-case behavior, which is not covered by an output schema and is not addressed in the description.

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 the format examples for from/to and the lang/video meanings are already documented. The description only restates that the read is bounded by two timestamps, adding little beyond what the schema already conveys.

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 verb (read) and resource (part of a transcript) plus the exact scoping mechanism (between two timestamps). The phrase 'Much smaller than the full transcript' implicitly distinguishes it from get_youtube_transcript, and the 'moment found with find_in_transcript' reference distinguishes it from the search sibling.

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?

Gives concrete usage contexts ('one chapter of a long podcast', 'the ten minutes around a moment found with find_in_transcript'), which shows the intended follow-up workflow after a search hit. It lacks an explicit 'use get_youtube_transcript instead when you need the whole thing' exclusion, so it stops short of 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.