Osiris Premiere MCP

Overview Schema Source Related Servers Discussions Admin

Select Clips By Pattern

select_clips_by_pattern

Selects every Nth clip that matches name, duration, track, time-range, or enabled filters, applies an offset, and reports the resulting selection count without editing the timeline.

Instructions

Select every Nth clip (with an offset) among clips that match optional name, duration, time-range, track, and enabled filters, then read back the selection count. Covers 'select every other clip on V1' and similar repetitive selections without changing the timeline.

Input Schema

TableJSON Schema

Name	Required	Description
`offset`	No	Zero-based index of the first candidate to select (default 0). Must be below every_nth.
`every_nth`	No	Select one clip out of every N candidates (default 1 = all candidates).
`name_regex`	No	Case-insensitive ECMAScript 3 compatible regular expression the clip name must match.
`track_type`	No	Track type to scan (default video).
`count_scope`	No	Whether the Nth count restarts on each track (default) or runs across all scanned tracks in timeline order.
`end_seconds`	No	Only clips overlapping before this sequence time.
`track_index`	No	Restrict to one track index.
`name_contains`	No	Case-insensitive substring the clip name must contain.
`start_seconds`	No	Only clips overlapping at or after this sequence time.
`add_to_selection`	No	Keep the existing selection instead of replacing it (default false).
`include_disabled`	No	Include disabled clips as candidates (default true).
`max_duration_seconds`	No	Maximum clip duration.
`min_duration_seconds`	No	Minimum clip duration.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.19.1Oct 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations carry the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description usefully clarifies that the mutation is only to selection state and that the timeline is untouched, resolving the apparent tension with readOnlyHint=false. It also mentions reading back the selection count, which is a behavioral detail beyond annotations.

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?

Two sentences, front-loaded with the core selection behavior, then the practical example. Efficient, though the first sentence is dense with a long filter enumeration that slightly slows parsing.

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, the return count needn't be explained, and annotations plus 100% schema coverage handle most details. The description's remaining gap is the replace-vs-append default of selection, which is left to the schema's add_to_selection parameter.

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% across all 13 parameters, so the schema already documents offset, every_nth, filters, and defaults. The description only summarizes categories (name, duration, time-range, track, enabled) without adding syntax or semantics beyond the schema, so the baseline of 3 applies.

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?

The description gives a specific verb (select), a precise resource (every Nth clip), and the pattern mechanism including offset, plus the filter dimensions. It clearly differentiates by mechanism from siblings like select_clips_by_name or select_clips_in_range, but never names an alternative explicitly.

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?

It provides a concrete use case ('select every other clip on V1') and notes it doesn't change the timeline, which implies when it applies. However, it never states when NOT to use it or which sibling to prefer for plain name-based or range-based selection, leaving routing to inference.

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

Deploy Server