Skip to main content
Glama
Sign In

switch

by ai.switchapp
OverviewDiscussionsAdmin

Generate Sound Effect

generate_sound_effect

Make one sound effect from plain words with ElevenLabs SFX v3 (it follows several instructions in one prompt, for example "crowd cheering, then a ball drops, then booing", and handles vocal and musical sounds): whooshes, impacts, chimes, clicks, risers, ambiences, foley, anything that is not music and not a voice. Describe the sound (what it is, its attack and tail, its material, its feel), optionally fix its length in seconds (0.5 to 30; leave it out to let the model pick), set loop true for a seamless ambience, prompt_influence 0 to 1 for how literally to follow the words, model "v3" (default) or "v2" (ElevenLabs suggests comparing both on your own prompts), and output_format (mp3 at 32 to 192 kbps, opus, wav or pcm at 8 to 48 kHz, or ulaw/alaw 8 kHz for phone audio; default mp3_44100_128). For a music bed use generate_sound. Billed 1 token per 7 seconds of sound, rounded up (a token quote applies) and the file is saved to your library. Returns audio_url, duration_seconds and generation_id.

Input Schema

NameRequiredDescriptionDefault
loopNoOptional. true makes a sound that loops seamlessly (ambiences, textures).
modelNoOptional. v3 (default, SFX v3: several instructions in one prompt, vocal and musical sounds) or v2.
secondsNoOptional length, 0.5 to 30 seconds. Leave out to let the sound maker choose from the words.
descriptionYesThe sound in plain words, as long as you like. For example "a glassy futuristic visor powering up, quick rising shimmer into a soft bright chime, clean, no music".
output_formatNoOptional file format, default mp3_44100_128. wav_48000 or pcm_48000 for editing, mp3_44100_192 for top mp3 quality, ulaw_8000 or alaw_8000 for phone systems.
prompt_influenceNoOptional, 0 to 1. Higher follows the words more literally with less variety. Default 0.3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / model
      Added value: +{
+  "description": "Optional. v3 (default, SFX v3: several instructions in one prompt, vocal and musical sounds) or v2.",
+  "enum": [
+    "v3",
+    "v2"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / output_format
      Added value: +{
+  "description": "Optional file format, default mp3_44100_128. wav_48000 or pcm_48000 for editing, mp3_44100_192 for top mp3 quality, ulaw_8000 or alaw_8000 for phone systems.",
+  "enum": [
+    "mp3_22050_32",
+    "mp3_24000_48",
+    "mp3_44100_32",
+    "mp3_44100_64",
+    "mp3_44100_96",
+    "mp3_44100_128",
+    "mp3_44100_192",
+    "opus_48000_32",
+    "opus_48000_64",
+    "opus_48000_96",
+    "opus_48000_128",
+    "opus_48000_192",
+    "wav_8000",
+    "wav_16000",
+    "wav_22050",
+    "wav_24000",
+    "wav_32000",
+    "wav_44100",
+    "wav_48000",
+    "pcm_8000",
+    "pcm_16000",
+    "pcm_22050",
+    "pcm_24000",
+    "pcm_32000",
+    "pcm_44100",
+    "pcm_48000",
+    "ulaw_8000",
+    "alaw_8000"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"The sound in plain words, under 450 characters. For example \"a glassy futuristic visor powering up, quick rising shimmer into a soft bright chime, clean, no music\"."New value: +"The sound in plain words, as long as you like. For example \"a glassy futuristic visor powering up, quick rising shimmer into a soft bright chime, clean, no music\"."
    • changedInput schema / properties / seconds / description
      Previous value: -"Optional length, 0.5 to 22 seconds. Leave out to let the sound maker choose from the words."New value: +"Optional length, 0.5 to 30 seconds. Leave out to let the sound maker choose from the words."
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost (1 token per 7 seconds rounded up, token quote applies), the side effect (file saved to your library), return fields (audio_url, duration_seconds, generation_id), and the provider's advice to A/B v2 vs v3. Annotations only say it is non-read-only, non-destructive and closed-world; the description supplies the consequential details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly with purpose and scope, but then walks through nearly every parameter at length (format bitrates, sample-rate families, exact ranges) that the 100%-covered schema already documents. It is information-dense but longer than its incremental value warrants.

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?

There is no output schema, yet the description names the return fields, the billing model, and where the artifact lands. For a 6-parameter generation tool with one required field and open cost implications, nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description adds genuine meaning: prompt_influence is framed as 'how literally to follow the words', and the model choice carries advice ('ElevenLabs suggests comparing both on your own prompts') absent from the schema. It largely restates formats and ranges that the schema already enumerates, which keeps it from a 5.

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?

States a specific verb+resource (make one sound effect) and draws hard scope boundaries: 'anything that is not music and not a voice', with named categories (whooshes, impacts, risers, foley). It also names the sibling it is not: 'For a music bed use generate_sound.'

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?

Explicit when-to-use ('anything that is not music and not a voice') and one explicit alternative (generate_sound for music beds), plus practical prompt advice and an optional-seconds rule. It does not address the other obvious alternates such as find_library_sound or extract_sound_effect, so the routing picture is incomplete but strong.

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

All switch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources