Skip to main content
Glama

Generate Sound Effect

generation_sound_create
DestructiveIdempotent

Queue a sound effect into the BlitzReels media library. Spends AI credits and returns a job to poll with generation_jobs_get.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "generation_sound_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
loopNoProduce a seamlessly loopable effect.
promptYesThe sound to create (3-500 characters).
workspaceIdNoOptional workspace ID. Defaults to the user's default workspace. UUID string.
idempotencyKeyNoRetry key. Reuse only with identical inputs.
durationSecondsNoEffect length between 0.5 and 30 seconds.
promptInfluenceNoHow literally to follow the prompt, between 0 and 1. Higher is more literal.

Output Schema

NameRequiredDescriptionDefault
generationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / generation / properties / app_url
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly=false, destructiveHint=true, idempotentHint=true and openWorldHint, so the bar is lower; the description still adds two facts annotations cannot convey — that credits are consumed and that the call is asynchronous and returns a job. It never explains what the destructiveHint actually means here (whether a prior asset is replaced), leaving one meaningful gap.

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 sentences with zero filler. The action and destination come first, then the cost warning and the polling handoff, so the reader gets the critical facts immediately.

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?

An output schema exists, so return values need not be explained, and the description correctly focuses on cost and the async job pattern. The only thing an agent might still want is clarification of the destructive behavior implied by annotations.

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 every parameter including loop, durationSeconds, promptInfluence and idempotencyKey is already documented in the schema. The description adds no semantics beyond that, which is the expected baseline when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: queue a sound effect into the BlitzReels media library. The word 'sound effect' implicitly separates it from generation_music_create and generation_voiceover_create, but no sibling other than generation_jobs_get is named explicitly.

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?

Gives clear workflow context by naming the follow-up tool: the returned job must be polled with generation_jobs_get. It stops short of stating when to pick this over generation_music_create for a similar audio need, so no explicit alternative-selection rule is present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources