Skip to main content
Glama

Set Item In Out

set_item_in_out

Sets in and out points on a project panel item to mark a source range for editing, then reports requested and applied frame-floored seconds.

Instructions

Set in and/or out points on a project item in the project panel (marks source range for editing). Premiere floors video marks to the media's own frame grid, so a mark is verified when it lands on the frame the request floors to (an exact frame boundary keeps its own frame); the result reports requested and applied seconds.

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": {
      "item_id": "<item_id>"
    },
    "name": "set_item_in_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesNode ID or name of the project item, or the sequence ID of a sequence
in_secondsNoIn point in seconds
media_typeNoMedia type: 1=video, 2=audio, 4=all (default: 4)
out_secondsNoOut point in seconds
idempotency_keyNoOptional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses genuinely useful behavior: Premiere floors video marks to the media frame grid, marks are verified against the floored frame, exact boundaries keep their own frame, and the result reports requested versus applied seconds. That is exactly the kind of non-obvious mutation semantics annotations cannot convey. It stops short of stating ordering constraints (e.g. out after in) or what happens when no mark is supplied for one side.

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 action and the resource, then the frame-flooring caveat. Dense but each clause carries information; the second sentence is long yet every part (flooring, verification rule, boundary exception, reported values) is load-bearing. Minor cost is the parenthetical placement breaking the flow.

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?

For a mutation tool with seven parameters, nested guard objects, and an output schema, the description covers the core semantics and the tricky frame-rounding behavior, and the output schema relieves it of explaining return values. Gaps are modest: no guidance on choosing between item/sequence targets or on how media_type interacts with the flooring rule.

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 the schema already documents all seven parameters, which sets the baseline at 3. The description does add a little meaning — "and/or" signals in_seconds and out_seconds are independently optional, and "requested and applied seconds" explains the relationship between what is sent and what lands — but it says nothing about media_type selection or the guard/idempotency parameters beyond what the schema states.

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 and resource ("Set in and/or out points on a project item in the project panel") plus a gloss on what that means ("marks source range for editing"). It is clear what the tool does, but it never distinguishes itself from close siblings such as set_source_in_out, set_sequence_in_out_points, or clear_item_in_out, so an agent must infer the boundary.

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?

Usage is implied by the parenthetical "marks source range for editing" and by the emphasis on project items, but there is no explicit when-to-use statement, no mention of when to use the sibling clear/sequence/source variants instead, and no stated prerequisites. The agent gets context but must reason about alternatives on its own.

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