Any Video to Text

Open a saved transcript

get_my_transcript

Read-onlyIdempotent

Get the full text of a transcript from My transcripts, by the id list_my_transcripts gives. Costs nothing and works however old it is.

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": {
      "id": "<id>"
    },
    "name": "get_my_transcript"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The id from list_my_transcripts.
`timestamps`	No	true for [mm:ss] timestamps on every line.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds two real traits not in them: there is no cost incurred and there is no age/retention limit on retrievable transcripts. It does not describe size limits or failure modes for an unknown id.

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 short sentences, no filler, with the lookup source front-loaded before the cost/retention reassurances. Every clause carries information.

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 two-parameter read tool with full schema coverage and no output schema, the description covers source of the id, that full text is returned, and that there is no cost or expiry. Minor gaps remain on behavior for an invalid or deleted id.

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 coverage is 100%, so the id provenance and the timestamps flag format are already fully documented in the schema. The description's mention that the id comes from list_my_transcripts duplicates the schema's own wording and adds nothing about the optional timestamps parameter; baseline 3 applies.

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?

Specific verb and resource ("Get the full text of a transcript") scoped to a named collection ("My transcripts"), which separates it from the sibling get_transcript that presumably targets video transcripts. An agent can pick this one without opening either schema.

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

Usage Guidelines4/5

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

It states the precondition clearly: the id must come from list_my_transcripts, which gives the agent an explicit call chain. It stops short of saying when to prefer this over get_transcript or what to do if the id is unknown/invalid, so no true when-not guidance.

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

All Any Video to Text 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?