Skip to main content
Glama
getopenscreen

OpenScreen

Official
by getopenscreen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

addTrims

Apply multiple trim ranges in one call, so bulk cuts like removing silences do not require a round trip per cut. Each invalid range is refused alone while valid ranges still apply.

Instructions

Add MANY trim ranges in one call: ranges is a list, each entry taking exactly the fields addTrim takes. Use this whenever you have more than one cut to make — 'remove the silences' on a half-hour recording is hundreds of cuts, and sending them one at a time costs one round trip each. Each range stands or falls ALONE: one that cannot be placed is refused by itself and listed in refused with its index and the reason, while every other range is still applied. Nothing is rolled back, so a single bad bound never costs you the rest. The result leads with requested / appliedCount / refusedCount so you can see a partial outcome without re-reading the document — report what was refused rather than claiming the whole list landed. A zoom HOLDS over its span: it animates in during the window just before startSec and out during the window just after endSec. Each move lasts 0.6 s + 0.55 s × ln(renderedScale) of SCREEN time (0.72 s at 1.25×, 0.82 s at 1.50×, 0.92 s at 1.80×, 1.03 s at 2.20×, 1.29 s at 3.50×, 1.49 s at 5.00×), so a speed region scales the timeline it covers by its speed: longer above 1×, shorter below. getCurrentDocument gives each zoom's zoomInFromSec and zoomOutUntilSec, in virtual seconds like the zoom. A trim inside either window cuts that move and the export jumps at the cut: leave the windows untrimmed. Two zooms at most 1.5 s apart on screen, on the same clip with no trim between them, are chained: the camera pans from one to the next over 1 s of screen time from the first one's end (panUntilSec), with no zoom-out or zoom-in between them. Each applied entry carries the same cutTransitions warning addTrim reports.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangesYes
projectIdNoThe project to act on, from listProjects. Omit it only for the project open in the OpenScreen editor, which works only while the app runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds a lot beyond that: partial-application semantics, 'Nothing is rolled back', per-index refusal reporting, the result shape (requested/appliedCount/refusedCount), the cutTransitions warning, and the zoom-hold/chaining side effects that can break a cut. That is real consequence disclosure an agent cannot get 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.

Conciseness3/5

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

Well front-loaded — batch purpose first, failure semantics second — but the back half drifts into extensive zoom timing lore (a full table of durations by scale) that arguably belongs in addZoom's documentation. The warning is relevant, yet the density of detail outweighs what an addTrims caller needs.

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?

With no output schema, the description carries the return contract itself (requested/appliedCount/refusedCount, refused entries with index and reason) and the partial-failure model, so an agent can both call and interpret the result correctly.

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 50% and the schema barely documents the array item shape; the description compensates by explaining that `ranges` is a list whose entries take exactly addTrim's fields, and that refusals are reported with the entry's index. projectId is covered by the schema itself, so nothing important is left unclear.

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 (add) and resource (many trim ranges) with the key differentiator up front: batch versus the singular addTrim. An agent immediately knows this is the bulk variant and that each entry mirrors addTrim's fields.

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 an explicit switching rule — 'Use this whenever you have more than one cut to make' — plus the cost rationale (one round trip per single call). It also names the sibling implication (addTrim for singles) and adds negative guidance: 'leave the windows untrimmed' to avoid export jumps.

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