CueFrame

Get Transcript

get_transcript

Read-onlyIdempotent

Read exact source-time transcript words in bounded utterance pages. Word start/end values are seconds from the source media start. Default limit is 20; pass pagination.nextCursor as after for later pages. The formatter omits the unbounded fullText duplicate.

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

Input Schema

Name	Required	Description
`after`	No	Zero-based utterance cursor returned as pagination.nextCursor.
`limit`	No	Utterances per page.
`before`	No	Zero-based utterance cursor for a backward page. Do not combine with after.
`mediaItemId`	Yes	mediaItemId (path).

Output Schema

Name	Required	Description
`data`	No
`fullText`	No
`language`	No
`pagination`	No	Cursor pagination metadata.
`utterances`	No
`mediaItemId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 28, 2026
- addedInput schema / $defs
```
Added value: +{
+  "__schema0": {
+    "maximum": 100,
+    "minimum": 1,
+    "type": "integer"
+  }
+}
```
- addedInput schema / properties / limit / $ref
```
Added value: +"#/$defs/__schema0"
```
- removedInput schema / properties / limit / maximum
```
Removed value: -100
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- removedInput schema / properties / limit / type
```
Removed value: -"integer"
```
First observedOct 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds valuable behavioral context beyond annotations: source-time units are seconds from media start, results are bounded utterance pages, and the formatter omits the unbounded fullText duplicate.

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?

The description is short, front-loaded, and every sentence serves a purpose: it defines the read operation, units, pagination usage, default limit, and output omission behavior.

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 read-only annotations, full schema descriptions, and an output schema, the description is complete enough for correct invocation. The main remaining gap is that it does not route the agent away from the similar editorial_inspect_transcript sibling.

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 parameters are already well documented. The description reinforces the default limit and cursor relationship, but mostly repeats schema details and does not explain the before parameter or add much new parameter semantics.

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 clearly states a specific verb/resource: reading exact source-time transcript words in bounded utterance pages. It is understandable without opening the schema, but it does not distinguish this tool from the sibling editorial_inspect_transcript.

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?

It gives useful pagination guidance: default limit is 20 and pagination.nextCursor should be passed as after. However, it does not say when to use this tool versus related transcript or media-inspection siblings, nor does it provide exclusions.

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

All CueFrame tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.