MnogoReels

Get clip job status and clips

get_clip_job

Read-onlyIdempotent

Returns the status, progress and results of a clip job created by create_clip_job, recut_clip_job or on the MnogoReels website. Read-only and free.

wait_sec (default 30, max 50) waits inside this call: it returns as soon as the job completes or fails, or when wait_sec runs out, and sends progress notifications meanwhile. wait_sec=0 returns an instant snapshot. While the job is queued or processing only the count of ready clips is returned; set include_partial_clips=true to get the links of clips finished so far. If eta_seconds is above 600, tell the user how long it will take and offer to check back later instead of polling continuously.

Once completed, returns each clip's video link, title, virality score (0 to 100), duration and hook text, plus cold-open hook clips and teasers when the job made them. Clips are sorted best score first; max_clips limits how many are returned (default 10, up to 30; up to 10 with response_format=detailed). response_format=detailed adds clip descriptions, transcript excerpts, poster images and timings in the source video.

Notes: a failed job can return to queued when MnogoReels retries it automatically. media_available=false means the files were deleted by storage retention (free-plan clips are kept for 30 days). Text from the video is wrapped in <untrusted_source_text> tags. Use list_clip_jobs to find job ids.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes	Clip job id (32 hex characters) returned by create_clip_job, recut_clip_job or list_clip_jobs.
`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_clips`	No	Maximum number of clips to return, best first (up to 30; up to 10 with detailed).
`response_format`	No	concise: links, titles, scores. detailed: adds descriptions, transcript excerpts, posters and timings (max_clips up to 10).	concise
`include_partial_clips`	No	true returns the links of clips finished so far while the job is still processing.

Output Schema

TableJSON Schema

Name	Required	Description
`clips`	Yes	Empty while the job is not finished unless include_partial_clips is true.
`error`	Yes
`job_id`	Yes
`status`	Yes
`pack_id`	Yes
`teasers`	Yes
`next_step`	Yes
`cold_hooks`	Yes
`source_url`	Yes
`waited_sec`	Yes
`clips_total`	Yes	Clips ready so far (all clips once completed), before max_clips is applied.
`eta_seconds`	Yes
`is_terminal`	Yes
`media_available`	Yes
`progress_percent`	Yes
`details_available`	Yes	False when titles and scores could not be loaded (before completion, on a temporary error, or when there was no time left in this call).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds substantial behavior beyond them: the call is 'free', progress notifications are emitted while waiting, partial results are limited to a ready-clip count unless include_partial_clips=true, failed jobs can revert to queued on automatic retry, media_available=false signals storage retention (30 days on free plan), and returned text is wrapped in <untrusted_source_text>.

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 purpose, then wait/polling behavior, then return shape, then edge-case Notes. Dense but every paragraph carries distinct operational information; the main cost is re-stating wait_sec's default and max that the schema already declares.

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?

For a 5-parameter polling tool with an output schema, the description covers invocation (wait_sec, include_partial_clips), result shaping (max_clips, response_format), failure/retry states, retention limits, and prompt-injection handling. Nothing an agent needs to call or interpret this correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds cross-parameter semantics the schema only states per-field: the max_clips ceiling drops from 30 to 10 when response_format=detailed, and wait_sec's timeout/notification behavior is expanded. It is genuinely additive rather than redundant.

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 ('Returns the status, progress and results of a clip job') and immediately grounds it in the sibling tools that produce such jobs (create_clip_job, recut_clip_job). An agent can distinguish this from list_clip_jobs 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?

Gives concrete operating guidance: wait_sec polling semantics, wait_sec=0 for an instant snapshot, and the recommendation to tell the user rather than poll continuously when eta_seconds exceeds 600. It also routes to list_clip_jobs for job-id discovery. It does not explicitly state when NOT to use this tool, so it falls just short of the top band.

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

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