Skip to main content
Glama

transcript_summary

Summarize a video’s transcript into a compact overview of cue count, word count, speaking duration, top keywords, and timeline segments so you can quickly understand its content and structure.

Instructions

Return a compact, structured overview of a video's transcript: cue count, word count, speaking duration, top keywords, and timeline segments with representative lead lines. Much smaller than transcript_get on a long video, so reach for this first when asked what a video is about or how it is structured.

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

Input Schema

NameRequiredDescriptionDefault
fileNoOptional path to a video or subtitle file; defaults to the playing file
segmentsNoNumber of timeline segments to divide the transcript into (1-20, default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does reasonably well: it states the returned fields, characterizes the result as compact/aggregated rather than raw, and sets a cost expectation on long videos. It leaves read-only behavior implicit, but the read nature is clear from 'Return ... overview', and no mutation risk is suggested.

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 sentences, both earning their place: the first defines output, the second routes usage and cost. The most decision-relevant information (compact, smaller than transcript_get, use first) is front-loaded rather than buried.

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 summarization tool with no annotations and no output schema, the definition covers purpose, output shape, and selection guidance well enough to call it confidently. The only real gap is that it doesn't describe the response container (structure of keywords/segments) in more concrete terms, which matters slightly more given no output schema exists.

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 100%, so both the file default and the 1-20 segments range are already documented in the schema; a 3 is the baseline. The description does add a little meaning by tying 'segments' to the timeline output ('timeline segments with representative lead lines'), clarifying what the parameter produces, but it adds no format or granularity guidance beyond that.

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 opens with a specific verb and resource ('Return a compact, structured overview of a video's transcript') and enumerates the payload: cue count, word count, speaking duration, top keywords, and timeline segments. It also distinguishes itself from the sibling transcript_get by relative size, so an agent can choose between them without opening either 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 a clear trigger ('reach for this first when asked what a video is about or how it is structured') and frames the alternative via the size comparison with transcript_get. What it doesn't do is state the inverse condition explicitly — e.g. that you should switch to transcript_get when you need verbatim cue text or exact quotes.

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

Deploy Server

Other Tools