Skip to main content
Glama

transcript_rename_speaker

Rename a speaker label across a transcript, such as changing "Speaker 1" to "Host," and persist the change so later transcript, search, and summary calls show the updated name.

Instructions

Rename a speaker label across the transcript (e.g. from "Speaker 1" to "Host" or "Alice"). The rename is persisted in cache so subsequent transcript_get, search_transcript, and transcript_summary calls reflect it.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "transcript_rename_speaker"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesNew speaker name
fileNoOptional path to a video or subtitle file; defaults to the playing file
fromYesExisting speaker name to replace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 burden. It usefully discloses a side effect beyond the action itself: the rename is persisted in cache so transcript_get, search_transcript, and transcript_summary reflect it later. It does not say whether the change is reversible, whether it applies to every occurrence or just the current view, what happens if "from" does not match, or whether persistence survives restarts.

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, action first, consequence second, zero filler. The example is embedded rather than given its own sentence, which keeps it tight.

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 three-parameter mutation with no annotations or output schema, the description covers what it does and the persistence consequence. It is only missing edge behavior (no match found, per-file scoping via "file") that an agent would want before invoking.

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 coverage is 100%, so the baseline is 3, and the description adds a little on top by illustrating the semantic meaning of from/to with realistic label values. It says nothing about the optional "file" parameter's effect on scope of the rename, which keeps it from a 5.

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 and resource ("Rename a speaker label across the transcript") and gives a concrete before/after example ("Speaker 1" to "Host"). The scope word "speaker" cleanly separates it from the sibling bookmark_rename without needing to name it.

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?

Usage is only implied: an agent can infer you call this when labels are generic and you want readable output. There is no explicit when-to-use statement, no mention of transcript_speakers or transcript_get as the way to discover existing labels, and no stated exclusions or prerequisites.

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