Skip to main content
Glama
Podcast MCP
by calebn

split_clip_tool

Split audio clips at a specified timeline timecode to create precise blade cuts, including multi-track edits across selected dialogue tracks.

Instructions

Split clip(s) at a timeline timecode.

Pass track_ids for multi-track blade cuts. When omitted, uses track_id / speaker, or all dialogue tracks. Submits SplitAtTime on the document plane (same path as ShareCut Studio blade).

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": {
      "at_time": "<at_time>"
    },
    "name": "split_clip_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
at_timeYes
speakerNo
track_idNo
track_idsNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • addedInput schema / properties / track_ids
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Track Ids"
      +}
    • removedInput schema / properties / track_ids_json
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Track Ids Json"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "project_path",
      -  "at_time"
      -]New value: +[
      +  "at_time"
      +]
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses the fallback resolution order and names the underlying operation ('Submits SplitAtTime on the document plane'), which signals a mutation on the project document. It omits reversibility/undo, whether project_path must point to an open project, and any permission or side-effect warnings for a destructive blade cut.

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?

Four short lines, front-loaded with the core action before the parameter branching, with no redundant restatement of the name. The closing 'ShareCut Studio blade' reference is flavor rather than instruction, but it is brief enough not to distract.

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

Completeness3/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 explained, and the sibling list is not the description's responsibility. Against a mutation tool with no annotations and 0% schema coverage, though, the definition should specify the timecode format and the project_path parameter, which are the two things most likely to cause a wrong call.

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 coverage is 0%, so the description must compensate: it usefully defines the track_ids vs track_id/speaker precedence and implicitly scopes at_time to a 'timeline timecode'. However, at_time is typed as a bare number with no stated unit, frame base, or format, and project_path is never mentioned at all — a meaningful gap given five undocumented parameters.

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?

States a specific verb and resource ('Split clip(s)') and the axis of the cut ('at a timeline timecode'), which is concrete and actionable. It does not differentiate from the sibling speaker_split_tool even though the mention of a 'speaker' fallback suggests overlap, leaving the agent to infer which split tool to pick.

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?

The description explains internal branching ('Pass track_ids for multi-track blade cuts'; fallback to track_id / speaker, then all dialogue tracks), which helps the agent decide what to pass. It gives no guidance on when to choose this tool versus speaker_split_tool or the other clip-editing siblings, and no preconditions for use.

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

Deploy Server

Other Tools