Any Video to Text

Check a transcript job

transcribe_status

Idempotent

Check a transcript that get_transcript or summarize_video said is still running, using the jobId they returned. Waits up to about 20 seconds, then returns the finished transcript (same format as get_transcript) or says it is still running, in which case call it again. Only works for jobs started by your own account.

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": {
      "jobId": "<jobId>"
    },
    "name": "transcribe_status"
  }
}

Input Schema

Name	Required	Description	Default
`jobId`	Yes	The jobId returned by get_transcript or summarize_video.
`timestamps`	No	true for [mm:ss] timestamps on every line.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only give generic flags (idempotent, non-destructive, open-world); the description supplies the operationally critical details: a ~20 second blocking wait, two possible outcomes (finished transcript vs. still-running), and the instruction to re-poll on the latter. The account-scoping constraint adds an auth boundary the annotations cannot express.

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, zero filler. The precondition is front-loaded before the polling behavior, and the return/retry semantics follow in the order an agent needs them.

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

Completeness5/5

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

Despite having no output schema, the description says what comes back ("same format as get_transcript") and covers the alternate branch. Combined with the wait duration and scope limit, an agent has everything needed to call and loop correctly.

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 both jobId and timestamps are already documented in the schema and the baseline is 3. The description reinforces where jobId comes from but adds nothing about the timestamps flag, so it does not exceed 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?

"Check a transcript ... using the jobId they returned" states a specific verb (check) and resource (transcript job), and explicitly positions the tool downstream of get_transcript and summarize_video. An agent can immediately tell this is the polling endpoint, not a fetch-by-id endpoint.

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 names the exact triggering condition (get_transcript or summarize_video said the job is still running), the correct input source (the jobId those tools returned), and the retry action ("call it again"). It also states a hard exclusion: "Only works for jobs started by your own account."

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?