Skip to main content
Glama
Sign In
Reedapt MCP server

Reedapt MCP server

Official
by Reedapt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a dub's transcript

get_transcript
Read-only

Retrieve a completed dub’s transcript in time order, including speaker, original and dubbed lines with millisecond timestamps; paginate 200 lines at a time using offset.

Instructions

A completed dub's lines in time order: speaker, original words and the dubbed words, with times in milliseconds. Returns 200 lines at a time; use offset for more.

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": {
      "dub_id": "<dub_id>"
    },
    "name": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
dub_idYesThe dub's id, such as dub_…
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, open-world operation, so the bar is lower. The description still adds real behavior: page size of 200 lines, offset-based pagination, millisecond time units, and the completed-dub precondition. It stops short of saying what happens on an unfinished dub or whether a total count is returned.

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, no filler. Return shape comes first, pagination second, which is the right order for an agent deciding how to call it.

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 carries the burden of describing the return value and does so concretely (speaker, original words, dubbed words, millisecond times). The pagination contract is stated. Minor gap: no guidance on incomplete dubs or how to know when paging is exhausted.

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 only 50%: dub_id is documented but offset has no description, just a default and bounds. The description compensates by explaining that offset pages through results beyond the 200-line window, which is the key meaning an agent needs. The mechanism behind dub_id's format is already covered by the schema.

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 names a specific resource and its exact contents: 'A completed dub's lines in time order: speaker, original words and the dubbed words, with times in milliseconds.' That is far more informative than the title alone. It does not distinguish itself from the sibling get_subtitles, which plausibly overlaps, so it falls short of a 5.

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 phrase 'A completed dub's' implies a precondition (the dub must be finished), and 'use offset for more' gives guidance on retrieving further pages. But there is no explicit statement of when to prefer this over get_subtitles or get_dub, and no stated behavior when the dub is still in progress.

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