Retrieves the active sequence's settings, playhead position, in/out points, and track details (clips, mute, lock, target states) from the Premiere Pro timeline so you can inspect state before editing.
Overview of the sequence open in the timeline: settings, playhead, in/out, every track (clips, muted, locked, targeted)
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full load. It discloses what comes back in useful detail (settings, playhead, in/out, all tracks and their clips/flags), which is valuable, but it says nothing about behaviour when no sequence is open, whether the call is expensive on large sequences, or whether data is live versus cached.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with the resource front-loaded ('Overview of the sequence open in the timeline') followed by the payload inventory in a parenthetical. No filler, no repetition of the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description does the work of outlining the return value field by field, which is what an agent needs to decide whether to call it. It falls short only on failure modes and result size, which are the remaining unknowns for a parameterless aggregate read.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is trivially 100% for an empty object.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb+resource: retrieves an overview of the sequence currently open in the timeline, and it enumerates the payload (settings, playhead, in/out, tracks with clips/muted/locked/targeted). That enumeration distinguishes it in practice from get_sequence_settings, get_track_info and get_playhead, though it never names those siblings explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The word 'Overview' implies the orienting use case — grab a single snapshot instead of calling the granular getters — but no when-to-use, when-not-to-use or alternative is stated. An agent must infer that this is the aggregate read versus the per-track/per-setting tools in the sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.