Slice

Restyle a clip

restyle_clip

Use this when the user wants a made clip changed and rendered again: a different caption style, bigger or smaller captions, captions moved up or down, the hook title turned on, off or reworded, or the whole video shown instead of cropped (fit, background). The change is saved on the clip and a new render starts; follow with get_job. When the user wants the look kept for future clips, pass save_as_default (new clips then start from it). Do not use for clips that have not been made yet (use make_clips). When the person is watching in Slice and you are fixing a clip step by step, prefer the tools that change the saved clip without a render (cut_words, set_hook_title, edit_captions, set_trim, set_caption_style, set_frame) and export once at the end: export true with nothing else makes the video from the clip exactly as it stands.

Input Schema

Name	Required	Description
`fit`	No	How the picture sits in the frame. "fill" (the default) crops it to fill the frame. "whole" shows the whole video, nothing cropped, with space around it; use when the user does not want a wide video cropped.
`style`	No	A caption style id or name from list_styles, e.g. bold-punch.
`export`	No	True with nothing else to change: make the video from the clip as it stands now (after edits with the no-render tools).
`clip_id`	Yes	The clip_id from get_episode or get_job (or the job_id of its render). With episode_id, the clip's number or ref also works.
`position`	No	Where the captions sit. "up" and "down" move them from where they are now.
`background`	No	What fills the space around a whole video: "black", or "blur" for a blurred copy of the video. Only matters with fit "whole".
`episode_id`	No	Only needed when clip_id is a number or ref from get_episode.
`hook_title`	No	The title box at the top of the clip, on by default for new clips. false removes it, true puts the clip's title there, or give the words to show.
`caption_size`	No	Caption size. "bigger" and "smaller" are relative to now.
`save_as_default`	No	True when the user wants this look kept for future clips ("use this from now on", "save this style"). Can be sent with no other change to keep the clip's current look.

Output Schema

Name	Required	Description
`job_id`	Yes	Pass to get_job.
`status`	Yes
`changes`	Yes
`clip_id`	Yes
`message`	Yes
`saved_as_default`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / export

Added value: +{
+  "description": "True with nothing else to change: make the video from the clip as it stands now (after edits with the no-render tools).",
+  "type": "boolean"
+}

First observedOct 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations establish it is a non-read-only, non-destructive local action; the description adds the key side effects an annotation cannot cover: the change is saved on the clip and a new render starts, followed by get_job. It further explains that save_as_default persists the look to future clips, and clarifies the export-only path.

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 the trigger and the editable dimensions, then routing to alternatives, then the export path. It is dense and long but nearly every clause carries routing or behavioral information; only the parenthetical tool list is slightly bulky.

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?

With 10 parameters, 100% schema coverage, annotations, and an output schema, the description supplies the remaining context: render side effect, follow-up with get_job, persistence semantics, and the no-render alternative workflow. Nothing needed to invoke it 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 adds meaning about relative edits ('bigger or smaller captions', 'captions moved up or down'), the boolean-or-string form of hook_title, and the interaction between fit and background. It stops short of adding syntax beyond what the schema already provides.

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?

Names a specific verb and resource ('restyle a clip') and enumerates the exact changes it can make: caption style, size, position, hook title, fit/background. It also explicitly separates itself from make_clips (unmade clips) and the no-render edit tools, so an agent can pick it correctly without opening 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 Guidelines5/5

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

Explicit when-to-use ('user wants a made clip changed and rendered again'), when-not ('clips that have not been made yet (use make_clips)'), and named alternatives for step-by-step editing with a single export at the end. The save_as_default condition is also stated in user-language terms.

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?