Samplecut

Adjust clip

retrim_clip

Re-cut a clip from Samplecut's clip card to a new start/end, reusing the audio already extracted for it. Called by the interactive card; to cut something new, use cut_audio.

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": {
      "clip_id": "<clip_id>",
      "start_sec": "<start_sec>",
      "end_sec": "<end_sec>"
    },
    "name": "retrim_clip"
  }
}

Input Schema

Name	Required	Description
`format`	No	Download format; default the clip's current format
`clip_id`	Yes	clip_id from a cut_audio result
`context`	No	Optional: why the clip is being re-cut
`end_sec`	Yes	New range end in seconds
`llm_model`	No	Optional: the model making this call
`start_sec`	Yes	New range start in seconds
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

Name	Required	Description	Default
`full`	Yes
`peaks`	Yes
`title`	Yes
`format`	Yes
`clip_id`	Yes
`end_sec`	No
`filename`	Yes
`start_sec`	No
`editor_url`	Yes
`expires_at`	Yes
`download_url`	Yes
`track_duration_sec`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 13, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Optional: why the clip is being re-cut",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "Optional: the model making this call",
+  "type": "string"
+}

AddedSep 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the audio is reused rather than re-extracted, and the tool is invoked from the interactive card. It stops short of saying whether the prior clip is overwritten or whether clip_id remains valid.

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

Conciseness5/5

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

Two short sentences, zero filler, with the operation and its reuse-of-audio behavior front-loaded before the routing hint to cut_audio.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description covers purpose, alternative routing, and invocation source. It leaves minor gaps about the fate of the original clip and whether the re-cut replaces or versions it, which matters for a non-read-only tool.

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 description coverage is 100%, so every parameter is already documented, including the conversation_id protocol and format default. The description's 'new start/end' merely restates start_sec/end_sec and adds no syntax or constraint detail beyond the schema. Baseline 3 applies.

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 (re-cut), resource (clip), and the resulting scope (new start/end), and explicitly distinguishes itself from the sibling cut_audio. An agent can tell it apart from cut_audio and get_transcript without opening any schema.

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?

Names the alternative explicitly ('to cut something new, use cut_audio') and gives the invocation context ('Called by the interactive card'), so the when-to-use and when-to-use-something-else conditions are both covered.

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

All Samplecut tools Inspect

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

Need Help?