BlitzReels Video Editor

Generate Sound Effect

generation_sound_create

Idempotent

Queue a sound effect 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
`loop`	No	Produce a seamlessly loopable effect.
`prompt`	Yes	The sound to create (3-500 characters).
`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	Effect length between 0.5 and 30 seconds.
`promptInfluence`	No	How literally to follow the prompt, between 0 and 1. Higher is more literal.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`generation`	Yes

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond annotations by revealing the asynchronous nature ('Queue'), the cost implication ('Spends AI credits'), and the return of a job to poll with generation_jobs_get. Annotations only cover read-only/idempotent/destructive hints, so this adds substantial behavioral context.

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?

Two concise sentences with the core purpose front-loaded. Every word earns its place, and the job-polling hint is included without unnecessary detail.

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 full schema coverage and an output schema, the description fills the remaining gaps: async job model, credit cost, and media library destination. This is complete for the tool's complexity.

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 coverage is 100% with detailed parameter descriptions, so the baseline is 3. The description adds no param-specific meaning, but the schema already handles it.

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?

Clearly states it queues a sound effect into the BlitzReels media library, distinguishing it from sibling generation tools for music, image, video, and voiceover. Also mentions returning a job to poll, which clarifies its role.

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?

Provides clear context: use for sound effects, spends AI credits, returns a job for polling. It doesn't explicitly name alternatives, but the sound-effect scope and job-based workflow make the usage unambiguous.

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?