Skip to main content
Glama
getopenscreen

OpenScreen

Official
by getopenscreen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

addZooms

Batch-add multiple zoom regions in one call for smart-zoom passes, reducing round trips; each region is applied or refused independently.

Instructions

Add MANY zooms in one call: regions is a list, each entry taking exactly the fields addZoom takes (same depth table, 1=1.25×, 2=1.50×, 3=1.80×, 4=2.20×, 5=3.50×, 6=5.00×). Use this for the smart-zoom pass, where you have decided every zoom before emitting the first one — sending them one at a time costs one round trip each. Each region stands or falls ALONE: one that covers no clip is refused by itself and listed in refused with its index and the reason, while the others are still applied. The result leads with requested / appliedCount / refusedCount, and each applied entry carries its renderedScale — quote that, never the depth — plus the same cursorAnchor addZoom reports, whenever the footage under that region has readable pointer telemetry, and the same cutTransitions warning. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionsYes
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.8/5.0
Behavior5/5

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

Annotations cover only the generic safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds substantial non-obvious behavior: each region is independent and can be refused individually with index and reason, the result leads with requested/appliedCount/refusedCount, applied entries carry renderedScale rather than depth, plus cursorAnchor and cutTransitions. It also discloses timing/hold semantics and chaining rules that materially affect correct invocation.

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?

Front-loaded with the core batch/independent-failure point, then progressively details timing and chaining. Every sentence carries operational information, but the single dense block on move duration formulas and chaining is heavy and would scan better segmented; no sentence is pure filler, though the duration table is arguably more detail than a selection decision 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?

There is no output schema, so the description rightfully covers the return shape (requested/appliedCount/refusedCount, renderedScale, cursorAnchor, cutTransitions), the failure mode, and the timing/trim constraints an agent must respect. Given the tool's complexity, nothing needed to call it correctly appears to be missing.

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 description coverage is 50%, and the description compensates well for the undocumented parts by spelling out the depth→scale table (1=1.25× … 6=5.00×) and the temporal semantics of startSec/endSec (hold windows, move duration formula in screen time, trim interaction, chaining distance). It does not mention projectId, which the schema does document, so the gap is minor rather than disqualifying.

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 precise verb+resource+scope: 'Add MANY zooms in one call', and explicitly contrasts with the sibling addZoom by noting each entry takes exactly the fields addZoom takes. An agent can immediately distinguish this batch tool from addZoom/addAutoZooms/setZoom 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?

Explicitly names the use case ('the smart-zoom pass, where you have decided every zoom before emitting the first one') and the cost trade-off that selects it over per-zoom calls ('sending them one at a time costs one round trip each'). Also states the per-item failure model, which is a usage-relevant guarantee.

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