Slice

Get a clip job

get_job

Read-only

Use this when the user wants to know whether a clip is cut or rendered, or wants the finished file. Pass the job_id from make_clips or restyle_clip, or a clip_id for that clip's latest render. Returns the status, progress, a still from the clip and, when finished, a short download link. Pass wait: true to hold on up to about 40 seconds for it to finish. Do not use for transcribe_audio jobs.

Input Schema

Name	Required	Description
`wait`	No	Wait briefly for it to finish instead of reporting now.
`job_id`	No	From make_clips or restyle_clip.
`clip_id`	No	A cut clip, for its latest render.

Output Schema

Name	Required	Description
`kind`	Yes
`clips`	No	For a cut: the clips it made, and the render that follows each.
`stage`	No	The step the job is on, as the worker reports it.
`title`	No
`job_id`	Yes
`status`	Yes
`clip_id`	No
`message`	Yes
`poster_url`	No
`download_url`	No	A short link that downloads the MP4. Good for 7 days.
`file_size_mb`	No
`progress_percent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedOutput schema / properties / stage

Added value: +{
+  "description": "The step the job is on, as the worker reports it.",
+  "type": "string"
+}

First observedOct 17, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description is free to add what they can't: the response payload (status, progress, still, download link) and the blocking behavior of wait: true ('hold on up to about 40 seconds'). The latency disclosure is exactly the kind of trait 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?

Front-loaded with the use case, then input sourcing, then return shape, then the wait flag, then the exclusion. Every sentence carries distinct information with no restatement of the name or title.

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?

An output schema exists so return values are technically optional to describe, yet the description still previews them usefully. Combined with input sourcing, the exclusion, and the wait-time bound, nothing an agent needs to invoke 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 coverage is 100%, so the baseline is 3, but the description goes beyond it: it tells the agent where each ID comes from and quantifies wait as 'about 40 seconds' where the schema only says 'briefly'. Only the mutual exclusivity of job_id vs clip_id is left implicit.

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+resource ('know whether a clip is cut or rendered, or wants the finished file') for a job-status tool. It names the siblings that produce a job_id (make_clips, restyle_clip) and explicitly rules out transcribe_audio jobs, so an agent can separate it from transcription_status without reading schemas.

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?

Gives concrete triggering conditions, two alternative input paths (job_id from a creation tool, or clip_id for the latest render), and an explicit exclusion: 'Do not use for transcribe_audio jobs.' That is when/when-not/alternatives all in one place.

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

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