Tool sound preferences can be saved, but the current webhook editor has no supplied sound-preview assets. A disabled preview control is not playable audio. Live conversation playback and timing remain unverified and unavailable through this guide.
Review the stored preferences
The intended behavior of
auto is to associate the sound with pre-tool speech; always requests it for every invocation. These are requested settings, not evidence that playback occurred.
Prepare a sound preference
1
Open an existing webhook tool
Use the signed-in Tools dashboard. Open Advanced, then review Tool call sound. Personal API keys cannot manage these tool resources.
2
Choose whether a sound is appropriate
Select None for
null, or one of the listed presets. Consider whether an extra sound would compete with spoken instructions or accessibility needs. Do not upload a custom track through an invented sound field.3
Review timing and save
When a sound is selected, review Sound behavior: With pre-speech maps to
auto, and Always play maps to always. Save the tool, reopen it, and check the persisted values. Keep actual listening and timing verification pending.tool_call_sound: "off" requests silence, while null means inherit the server setting. Do not put "off" in an ordinary webhook or client tool’s sound field.
Frequently asked questions
Does a sound indicate that the action succeeded?
Does a sound indicate that the action succeeded?
No. A progress cue is separate from the tool’s result. Confirm completion from the action’s actual response when a supported execution path is available.
Is this the conversation's background audio?
Is this the conversation's background audio?
No. Audio environment describes separate background-sound settings. Neither configuration proves live playback.