BlitzReels Video Editor

Create Clips

clips_create

Create a private BlitzReels clip batch from an existing asset or a user-provided video URL. Supports public social videos, Google Drive, and direct media URLs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No	Video URL to import before clipping. Supports social video links, Google Drive file links, and direct video file URLs.
`assetId`	No	Existing BlitzReels video asset ID. Provide assetId or url, not both. UUID string.
`workspaceId`	No	Optional workspace ID. Defaults to the user's default workspace. UUID string.
`clipPresetId`	No	Clip style preset. Use high-retention for High Retention clips or demo-focus for product and screen demos.	default
`captionThemeId`	No	Optional saved caption theme ID. Null uses workspace default captions. UUID string.
`idempotencyKey`	No	Retry key. Reuse only with identical inputs.
`autoTrimSilence`	No	Trim silence around selected moments.
`createSharePage`	No	Create a public showcase page where completed clips appear.
`confirmRightsToMedia`	No	Set true only after the user confirms they own the media or have permission to import it. Not needed for an existing BlitzReels asset.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`batch`	Yes
`result`	Yes

TDQS

A3.9/5.0

Behavior3/5

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

The annotations already indicate this is a non-read-only, non-idempotent creation operation. The description adds useful context that the result is a 'private' 'clip batch' and enumerates supported URL sources, but it does not disclose behavioral details such as async execution, the need for media rights confirmation, or what happens after batch creation.

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?

The description is two concise sentences with no filler. It front-loads the core action and resource, then adds the most relevant source-type details. Every sentence earns its place.

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

Completeness3/5

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

The description covers the primary use case but does not explicitly state that one of assetId or url is required, which is important given the schema marks all parameters as optional. It also does not mention asynchronous behavior or follow-up actions, though the presence of an output schema mitigates some of this gap.

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 the schema fully documents all 9 parameters. The description adds no parameter-level meaning beyond the schema; it only restates that the tool works from an asset or URL, which the schema already captures.

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?

The description states a specific action ('Create'), a specific resource ('private BlitzReels clip batch'), and the source inputs ('existing asset or user-provided video URL'). It clearly distinguishes this creation tool from sibling tools like clips_get and clips_manage by focusing on creation from a media source.

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?

The description gives clear context for when to use the tool: when creating a clip batch from an existing BlitzReels asset or a user-provided URL, including social, Google Drive, and direct media URLs. It does not explicitly name sibling alternatives or state when not to use the tool, but the intended usage is clear.

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

All BlitzReels Video Editor tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0

Disambiguation3/5

Most tools use clear domain prefixes, but several boundaries are fuzzy: clips_get and clips_manage both expose clip/export status, and update_timeline_clip overlaps with timeline_edit_apply for trim/duration changes. Detailed descriptions mitigate this, but an agent could still select the wrong tool for clip inspection or timeline edits.

Naming Consistency3/5

All names are snake_case and mostly readable, but the server mixes verb-first names (add_text_overlay, delete_timeline_items, update_timeline_clip) with noun-first domain-action names (clips_create, generation_*_create, media_import_*). The domain-prefix pattern dominates, yet the inconsistent verb placement makes the convention only partially predictable.

Tool Count1/5

58 tools is far beyond the 25+ threshold and matches the rubric's 50+ extreme-mismatch example. Even though the domain is broad, this surface would be easier for an agent to navigate if split into focused servers for media, generation, timeline editing, clips, and workflows.

Completeness3/5

Core video-editing flows are well represented: project creation/inspection, timeline item editing/deletion, media import/upload, AI generation, exports, and clips. However, lifecycle gaps remain—no project update/delete, no media asset deletion, no delete for characters or story kits, and no export cancellation—so some user requests will dead-end.

Resources

Need Help?