Skip to main content
Glama

detect_scene_cuts

Read-onlyIdempotent

Find hard cuts inside a source video asset. Read-only; returns cut times and the shots between them in source seconds, for writing a submit_video_remake plan. Analyses at most 120 s per call: pass start and end for a later part. Runs on ChatCut cloud machines: the first call can take about a minute while one starts; if it reports the analysis is still running, call again with the same arguments. Flashes and dissolves may need inspect_asset to confirm. A false cut is harmless in a plan; a missed cut is not.

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": {
      "assetId": "<assetId>"
    },
    "name": "detect_scene_cuts"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd of the range, in source seconds. Default video end. At most 120 s are analysed per call.
startNoStart of the range to analyse, in source seconds. Default 0.
assetIdYesSource video asset ID or unambiguous prefix in this Project.
projectIdNoFull project UUID. Required for external browser work; internal agents may omit. Execution/explicit-timeline calls never change later calls' target.
timelineIdNoFull timeline UUID, not a prefix. Required for browser work, even unplaced assets. Get it from read_project or manage_timelines action="list". Never switches visible timeline.
idempotencyKeyNoStable key for this browser execution. Reuse only with identical scope and parameters after a lost acknowledgement; applies only to this call.
browserProfileIdNoOptional browser profile override. Omit to select automatically; do not ask the user to choose.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive, and the description adds material context beyond them: execution on cloud machines, a ~1 minute cold-start latency on the first call, the still-running poll-and-retry behavior, and a risk stance (false cut harmless, missed cut costly). These are exactly the operational traits an agent cannot infer from structured fields.

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?

Five tight sentences, each carrying distinct information, with the core action and output format front-loaded before operational caveats. No filler or repetition despite covering purpose, limits, retry, alternatives, and risk.

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 seven-parameter tool with no output schema, the description fully specifies return values (cut times and shots in source seconds), the chunking constraint, latency, and retry semantics. Nothing essential to calling it correctly or interpreting results is missing.

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 all seven parameters including start, end, and assetId are already documented. The description restates the 120 s analysis window and the start/end chunking strategy, which reinforces but does not extend the schema's parameter meaning; it says nothing about projectId, timelineId, or idempotencyKey.

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 and resource ('Find hard cuts inside a source video asset') plus the output format ('cut times and the shots between them in source seconds'), which distinguishes it from asset inspection tools. An agent can tell this apart from inspect_asset or submit_video_remake 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?

Gives the downstream purpose ('for writing a submit_video_remake plan'), the operational constraint (120 s per call, use start/end for later parts), the retry protocol ('call again with the same arguments'), and names the alternative for ambiguous cases ('Flashes and dissolves may need inspect_asset to confirm').

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.