BlitzReels Video Editor

Generate Music

generation_music_create

Idempotent

Queue a background music track into the BlitzReels media library. Spends AI credits and returns a job to poll with generation_jobs_get.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mood`	No	Track mood.	neutral
`prompt`	No	Optional description of the track.
`workspaceId`	No	Optional workspace ID. Defaults to the user's default workspace. UUID string.
`idempotencyKey`	No	Retry key. Reuse only with identical inputs.
`durationSeconds`	No	Track length between 10 and 120 seconds.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`generation`	Yes

TDQS

A4/5.0

Behavior4/5

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

The description adds valuable behavioral context by disclosing that the operation spends AI credits and returns a job to poll via generation_jobs_get. This goes beyond the annotations, which only indicate idempotency and non-destructiveness.

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 exactly two sentences, front-loading the core purpose and adding only essential behavioral context. No wasted words.

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

Completeness4/5

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

Given the schema covers all parameters and an output schema exists, the description sufficiently conveys the operation's purpose, cost, and async workflow. It is complete enough for an agent to invoke correctly.

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?

All 5 parameters are fully described in the input schema (100% coverage), so the description does not need to explain them. The description does not add additional parameter-level meaning, staying at the baseline.

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 clearly states the tool's function with a specific verb ('Queue') and resource ('background music track into the BlitzReels media library'), distinguishing it from sibling generation tools by specifying background music.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage for background music and mentions the asynchronous job pattern and AI credit cost, but it does not explicitly contrast with alternative generation tools such as generation_sound_create or generation_voiceover_create.

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?