MnogoReels MCP server

Get transcription

get_transcription

Read-onlyIdempotent

Check a transcription job and retrieve its status and transcript as plain text, SRT subtitles, or timed segments, with paging for long results.

Instructions

Returns the status and text of a transcription started with create_transcription. Read-only and free.

wait_sec (default 30, max 50) waits for completion inside this call; progress notifications are sent meanwhile. format selects the output: text (plain text, default), srt (subtitles with timecodes) or segments (one timed phrase per line). Long transcripts come in pages of up to max_chars characters; when truncated is true, call again with offset set to next_offset.

Returns status (queued, processing, completed, failed), progress_percent, the detected language, total_chars and the requested page. The transcript comes from the video and is wrapped in <untrusted_source_text> tags.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`format`	No	text = plain text; srt = subtitles with timecodes; segments = one timed phrase per line.	text
`offset`	No	Character offset of the page to return; pass next_offset from the previous call.
`wait_sec`	No	Seconds to wait inside this call for the job to finish (default 30, max 50; 0 = return a snapshot immediately). Progress notifications are sent while waiting.
`max_chars`	No	Maximum characters per page (1000–24000).
`transcription_id`	Yes	Id returned by create_transcription.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	Yes
`format`	Yes
`status`	Yes
`content`	Yes	The requested page, wrapped in <untrusted_source_text>; null until completed.
`language`	Yes
`truncated`	Yes
`waited_sec`	Yes
`is_terminal`	Yes
`next_offset`	Yes
`total_chars`	Yes
`progress_percent`	Yes
`transcription_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: the call is 'free,' waiting happens in-call with progress notifications, transcripts are paginated and how to continue, and the result is wrapped in <untrusted_source_text> tags (a prompt-injection warning). Annotations only cover the read-only/idempotent safety profile, so this is genuinely additive.

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?

Three short paragraphs, front-loaded with the core purpose and payload, then polling/format, then return shape. Slight redundancy with format descriptions already in the schema, but every part is relevant.

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 an output schema existing, the description sketches status values, pagination fields and the untrusted-source framing, so an agent knows exactly how to drive the polling/pagination loop and how to treat the returned text.

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% and the input schema already documents format values, wait_sec defaults/max and notifications, offset/next_offset, and max_chars bounds. The description largely restates these, so it meets the baseline without extending meaning.

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?

States a specific verb and resource and ties it explicitly to its sibling: 'the status and text of a transcription started with create_transcription.' An agent can immediately place it in the create/get lifecycle without reading the 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?

Gives clear operational guidance: wait_sec polls in-call with progress notifications, and when truncated is true you re-call with offset=next_offset. It doesn't name an alternative tool or state when not to use it, but the create_transcription linkage supplies context.

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