Skip to main content
Glama

voice_isolation

Isolates spoken voice from background noise on an audio track or timeline clips, with adjustable amount and enable/disable control.

Instructions

AI Voice Isolation (Studio) on an audio track ('A1') or on timeline clips (refs).

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": {
      "target": "<target>"
    },
    "name": "voice_isolation"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNo
targetYes
enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It does not state whether the operation is destructive or reversible, what amount controls, what 'enabled' means in context, whether Studio is required, or how long processing takes. The '(Studio)' hint is the only behavioral clue.

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?

The single sentence is front-loaded and contains no filler, but it is under-specified rather than genuinely concise. A slightly longer definition could have earned its place by covering the missing parameter and behavioral context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three undocumented parameters, no annotations, and no output schema, the description is incomplete. An agent knows the general purpose but lacks enough context to choose correct values for 'amount' and 'enabled', or to understand side effects on the target track or clips.

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

Parameters2/5

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

Schema description coverage is 0%, so all three parameters (amount, target, enabled) are undocumented in structured fields. The description adds meaning only for 'target' by giving two example forms ('A1' and refs); it does not explain the integer range or effect of 'amount' or the role of 'enabled'.

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

Purpose3/5

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

The description identifies the operation (AI Voice Isolation, Studio feature) and its two target modes (an audio track like 'A1' or timeline clip refs). However, there is no explicit verb such as 'apply' or 'enable', and no differentiation from siblings like audio_normalize or clip_ai, so an agent must infer how this differs from other audio-processing tools.

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

Usage Guidelines2/5

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

The parenthetical 'A1' or 'refs' hints at possible target inputs, but the description gives no guidance on when this tool should be used instead of adjacent tools (e.g., audio_normalize, clip_ai) and no exclusions or prerequisites beyond a vague '(Studio)' mention.

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