Skip to main content
Glama

transcript_speakers

List every speaker in a transcript with cue counts, word counts, speaking time, and first/last timestamps, and optionally run diarization to detect speakers when labels are missing.

Instructions

List all speakers in the transcript with cue count, word count, speaking duration, and first/last timestamp. Pass detect: true to run lightweight acoustic + conversational turn diarization when subtitles do not already carry speaker labels.

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_speakers"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoOptional path to a video or subtitle file; defaults to the playing file
countNoTarget number of speakers when detect=true (2-8)
detectNoRun automatic speaker diarization if true (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned fields and characterizes diarization as 'lightweight acoustic + conversational turn diarization,' which hints at cost, but it does not state whether diarization persists speaker labels, how long it takes, or whether the operation is purely read-only. Useful context is present but not complete for a zero-annotation tool.

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 sentences, front-loaded with the primary listing behavior and followed by the key conditional for `detect`. There is no filler; a small deduction because the return-field list crowds the first sentence slightly.

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?

With no output schema, the description correctly compensates by naming the fields returned. Three optional parameters and no annotations is a modest surface, and the only real omission is the persistence/side-effect behavior of `detect`.

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 the schema already documents `file`, `count` (2-8), and `detect` (default false). The description adds real meaning only for `detect` by explaining what it does and when to enable it; `file` and `count` are not elaborated beyond the schema, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource ('List all speakers in the transcript') and enumerates the returned metrics (cue count, word count, speaking duration, first/last timestamp), making it immediately distinguishable from retrieval tools like transcript_get. It never names a sibling tool explicitly, so sibling differentiation is implied by subject matter rather than stated.

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

Usage Guidelines3/5

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

The second sentence gives a genuine conditional for the `detect` parameter: enable it when subtitles do not already carry speaker labels. However, there is no guidance on when to choose this tool over transcript_get, transcript_summary, or search_transcript, so tool-level selection is left to inference.

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