AskEditor

Get clip transcript

get_clip_transcript

[read · costs credits] Read a clip's speech. Default 'vtt' is a compact WebVTT transcript ('00:12.340 --> 00:15.020 text' cues in TIMELINE time) — use it to understand what is said. Use to pick the lines for a hook, a title card or a reel, or to cut on a word ('words' gives per-word timings). Free within the plan's monthly minutes; kept on the file. Not for putting captions on screen (use generate_captions). Returns wordCount, startMs, endMs, credits_used and vtt, words or text. Related: add_hook, add_title_card, make_reel, generate_captions. Full docs: load_skill with tools: [name].

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": {
      "project_id": "<project_id>"
    },
    "name": "get_clip_transcript"
  }
}

Input Schema

Name	Required	Description
`id`	No	Video, audio or compound clip id (or a compound child's) from get_timeline.
`toMs`	No	To (ms).
`items`	No	Many clips at once, max 20, each with this tool's fields; fields beside it are defaults.
`limit`	No	words/compact: most returned. Default 400, compact 800.
`format`	No	vtt (default), words (per-word ms), compact (words as [text,startMs,endMs]), text.
`fromMs`	No	From (timeline ms).
`offset`	No	words/compact: skip this many. Default 0.
`script`	No	Default "native". "roman" (Latin transliteration) is not supported yet.
`language`	No	ISO code of the speech ("hi", "bn", "ta", …). Omit to detect.
`project_id`	Yes	The AskEditor project this acts on (from list_projects).
`approval_id`	No	Only when a previous call answered needs_approval: the approval_id it gave. Call again with it as soon as you have told the person where to approve: the call waits for their answer.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description discloses credit/minute cost, that the transcript is persisted on the file, the default format and time basis, and the returned fields – context annotations (readOnlyHint=false, idempotentHint=false) do not convey. Minor tension: it frames itself as a pure 'read' while readOnlyHint is false, though 'costs credits' partially reconciles that.

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?

Front-loaded with cost tag and primary use, and every clause carries information (cost, format, alternatives, returns, related tools). It is dense with parentheticals and cross-references, which makes it heavier than ideal but not wasteful.

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 11 parameters, no output schema, it still names the return fields (wordCount, startMs, endMs, credits_used, vtt/words/text) and the sibling tools to chain with. The approval_id retry flow and multi-clip 'items' behavior are left to the schema.

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 baseline is 3, but the description adds real interpretation: the vtt cue syntax and that timestamps are in timeline time, plus what 'words' is for (per-word cut timing). It does not add much on limit/offset/items beyond the schema.

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?

"Read a clip's speech" names a concrete verb and resource, and immediately specifies the default output shape ('vtt' WebVTT cues in timeline time). It is explicitly distinguished from the captioning sibling ('Not for putting captions on screen (use generate_captions)').

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

Usage Guidelines5/5

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

It gives positive triggers (pick lines for a hook, title card, reel, cut on a word) and an explicit exclusion routing to generate_captions. The cost model ('Free within the plan's monthly minutes; kept on the file') further informs when an agent can call it freely.

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

All AskEditor 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.

Resources

Need Help?