Skip to main content
Glama

Extract Sound Effect

extract_sound_effect

Pull one described sound out of your video, like "keyboard clicks", "camera shutter" or "page turning", and split it into single effects to hear, trim and save. Use the video already in the chat: put its file id or name in video_url; when it was sent earlier, not with the latest words, find it first among what was sent before. Never ask the person to send it again. Give the sound in a few words, and start_seconds and end_seconds when the person says where it is (leave them out to search the whole video). Priced at 1 token for each 10 seconds searched. It answers with a job_id: the clips come into the chat by themselves when done (about a minute). For where a job is, or to stop it, use sound_extraction_status with the job_id. The same request again answers the job already made and charges nothing. Clips are split where the sound goes quiet, which is a suggestion: music or speech under the sound can leave traces. When separation keeps too little of the sound (more than 10 dB under that part of the video) or fails, the clips are cut straight from the video's own sound instead: the answer says from "cut from the video", tell the person that anything else playing at that moment is in them too. A cut holds every sound in that part, one clip per sound, whatever words were asked: never ask again for other sounds in the same part, and give each clip its own name from where it sits. A failed separation is not charged.

Input Schema

NameRequiredDescriptionDefault
againNotrue only when the person asks to run the same extraction again (charged again).
soundYesThe sound to pull out in the person's own words, unchanged (they become the clip's name), e.g. "keyboard clicks".
video_urlYesThe video in this chat by its file id or name, or an https link.
end_secondsNoOptional, where it ends, in seconds.
start_secondsNoOptional, where the sound starts in the video, in seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sound / description
      Previous value: -"The sound to pull out in a few words, e.g. \"mechanical keyboard clicks\"."New value: +"The sound to pull out in the person's own words, unchanged (they become the clip's name), e.g. \"keyboard clicks\"."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing pricing, asynchronous completion, automatic clip delivery, idempotency, fallback behavior when separation fails, clip naming implications, and non-charging for failed separation. These details are important for a write operation that creates clips and spends tokens.

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

Conciseness4/5

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

The description is long and dense, but most of the length is earned by operational details an agent needs for correct invocation. It is front-loaded with the core purpose, though the single-paragraph structure and some run-on clauses reduce clarity slightly.

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?

For a complex asynchronous extraction tool with no output schema, the description covers the full lifecycle: input sourcing, pricing, job_id response, automatic delivery, fallback behavior, failure handling, and output semantics. Nothing essential for correct invocation 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 coverage is already 100%, so the baseline is 3, but the description adds practical meaning: how to source video_url from earlier chat messages, how to phrase sound, and what happens when start_seconds/end_seconds are omitted. It does not explicitly clarify the `again` parameter, but the schema itself documents that exception.

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?

The description states a specific verb and resource: pulling one described sound out of a video and splitting it into clips. It clearly distinguishes the operation from sibling tools such as sound_extraction_status by naming that tool for job status/stopping.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit guidance: use the video already in chat, find earlier-sent files before asking, put the file id/name in video_url, provide start/end only when the person specifies location, and use sound_extraction_status for status or cancellation. It also states that repeating the same request returns the existing job without charge.

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