Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_sequence_in_out_points

Define the in and out points on a Premiere Pro sequence timeline by specifying time values, so you can mark precise edit ranges before cutting or exporting.

Instructions

Sets the in and/or out points on a sequence timeline.

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": {
      "sequenceId": "<sequenceId>"
    },
    "name": "set_sequence_in_out_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
inPointNoThe in point in seconds
outPointNoThe out point in seconds
sequenceIdYesThe ID of the sequence

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations to declare safety or side effects, the description carries full responsibility but only says 'sets' without revealing behavior like partial updates, clearing behavior, playhead interaction, or errors. This leaves too much ambiguity for an operations tool.

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?

The description is a single, clear sentence that front-loads the primary verb and target, with no wasted words. It is concise while covering the essence of the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple setter with three parameters and no output schema, the description is adequate but incomplete. It does not explain what happens when only one point is provided, nor does it address sequence state requirements or relationship to related tools.

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?

The schema already documents all 100% of parameters, so the baseline of 3 applies. The description does not add meaning beyond the schema, nor does it clarify interactions between inPoint and outPoint, so 3 is appropriate.

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?

The description clearly states the tool sets in and/or out points on a sequence timeline, using a specific verb and resource. It distinguishes itself from sibling tools like get_sequence_in_out_points and clear_sequence_in_out by its action and target.

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?

The description implies the tool is for setting in/out points on a sequence, but it never explicitly discusses when to choose this over alternatives such as set_source_in_out or set_item_in_out. No prerequisites or exclusions are provided.

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