Clypmint

Read the spoken words

get_transcript

Read-onlyIdempotent

Spoken words (number, start, end, source number), paged. cut takes word numbers; fix_captions source numbers. Cost: Free.

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": "get_transcript"
  }
}

Input Schema

Name	Required	Description
`count`	No	How many words, 1 to 2000; 500 when left out.
`video_id`	No	Video; the open one if left out.
`from_word`	No	The first word number to read; 0 when left out.
`output_id`	No	Output id.
`base_version`	No	Version id.

Output Schema

Name	Required	Description	Default
`code`	No
`cost`	No
`error`	No
`state`	No
`status`	No
`dry_run`	No
`message`	No
`plan_id`	No
`style_id`	No
`video_id`	No
`available`	No
`import_id`	No
`output_id`	No
`studio_url`	No
`version_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedInput schema / properties / video_id / description

Previous value: -"The video; the open one when left out."New value: +"Video; the open one if left out."

Changed4 schema fields changedNov 6, 2026

changedInput schema / properties / base_version / description

Previous value: -"A version_id to read; the live version when left out."New value: +"Version id."

changedInput schema / properties / output_id / description

Previous value: -"An output (Short, hook, shape); the main video when left out."New value: +"Output id."

changedInput schema / properties / video_id / description

Previous value: -"The video, from list_videos."New value: +"The video; the open one when left out."

changedInput schema / required

Previous value: -[
-  "video_id"
-]New value: +[]

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / output_id / description

Previous value: -"A Short, hook or shape of the video; the main video when left out."New value: +"An output (Short, hook, shape); the main video when left out."

AddedOct 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond that: results are paged, and the call is free of cost, both of which affect how an agent should plan repeated calls.

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?

Extremely compact and front-loaded — the resource and returned fields come first, then the cross-tool note, then cost. The telegraphic, fragment-heavy phrasing borders on cryptic, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a paging tool with five optional parameters, the description never explains paging semantics (how to advance from_word, what happens at the end) or what 'source number' means, leaving real gaps.

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, but the description adds meaning the schema does not: it clarifies that word numbers are the currency consumed by cut and source numbers by fix_captions, which explains why an agent would page through words. It still leaves 'source number' itself undefined.

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 the resource (spoken words / transcript) and the returned fields (number, start, end, source number) plus the paged nature, so an agent knows this reads transcript words. It also distinguishes itself from siblings by noting that 'cut takes word numbers' and 'fix_captions source numbers', though the verb itself is only implied by the title rather than stated in the description.

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: the mention of cut and fix_captions tells the agent how the returned word/source numbers are consumed downstream, which hints at when this tool is a prerequisite. There is no explicit statement of when to call this versus alternatives (e.g., get_timeline, get_captions-style siblings) or any prerequisites.

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

All Clypmint 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?