Skip to main content
Glama

Generate Music

generation_music_create
DestructiveIdempotent

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generation_music_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNoTrack mood.neutral
promptNoOptional description of the track.
workspaceIdNoOptional workspace ID. Defaults to the user's default workspace. UUID string.
idempotencyKeyNoRetry key. Reuse only with identical inputs.
durationSecondsNoTrack length between 10 and 120 seconds.

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

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses two non-obvious behaviors: the call spends AI credits and returns an asynchronous job rather than the finished asset. That cost-and-async disclosure is genuinely valuable. It is silent on the meaning of destructiveHint=true for an additive create (cleanup/replace semantics) and on idempotencyKey retry behavior, which the schema only partly covers.

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 short sentences with zero waste. The cost warning and the async/polling contract are front-loaded immediately after the purpose, so an agent can act on them without further reading.

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 spelled out, and the description still tells the agent that the output is a pollable job. Cost and polling guidance make it callable as-is. Minor gap: no guidance on safe reuse of idempotencyKey on retry, despite idempotentHint=true.

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 the mood enum, duration bounds, and idempotency key is already documented. The description adds only the framing that the track is background music, without explaining how mood or duration interact or how prompt is used. Baseline 3 applies when the schema carries the semantics.

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?

"Queue a background music track into the BlitzReels media library" gives a specific verb, resource, and destination, and names the follow-up sibling generation_jobs_get. It does not distinguish itself from the other generation_*_create siblings (sound, voiceover, image, video), which an agent must infer from the word "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?

Usage is implied rather than stated: the description tells the agent to poll with generation_jobs_get after creating, which is a useful workflow cue. It gives no explicit when-to-use or when-not-to-use guidance relative to generation_sound_create, generation_voiceover_create, or generation_faceless_create.

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