Osiris Premiere MCP

Overview Schema Source Related Servers Discussions Admin

Create Bars And Tone

create_bars_and_tone

Create a Bars and Tone synthetic media item in an Adobe Premiere project for leader or calibration; returns its name, nodeId, and treePath.

Instructions

Create a Bars and Tone synthetic media item in the project (useful for leader/calibration). Returns the created item's name, nodeId, and treePath, found by reading the project back.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Name for the bars and tone item (default: 'Bars and Tone')
`width`	No	Frame width in pixels (default: 1920)
`bin_id`	No	Optional destination bin: node ID, slash-separated bin path from the project root, or bin name. The bin is resolved before anything is created; the item is moved there and its location read back.
`height`	No	Frame height in pixels (default: 1080)
`timebase`	No	Timebase as ticks-per-second string (default uses sequence timebase)
`audio_sample_rate`	No	Audio sample rate in Hz (default: 48000)
`pixel_aspect_numerator`	No	Pixel aspect ratio numerator (default: 1)
`pixel_aspect_denominator`	No	Pixel aspect ratio denominator (default: 1)

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.6/5.0

Behavior3/5

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

Annotations already declare the write nature, non-destructive and non-idempotent hints, so the description's main addition is the read-back verification and returned fields. It adds some behavioral detail but does not cover permissions, side effects, or reversibility beyond what annotations provide.

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?

Two sentences, front-loaded with the purpose and then the return information. No filler or redundancy.

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?

Given the rich schema (100% coverage), output schema, and annotations, the description supplies the essential purpose and return behavior. It omits only when-to-use guidance and explicit sibling alternatives, but those are not required for calling correctly given the structured data.

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 fully documents all eight parameters. The description does not add any parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource ('Create a Bars and Tone synthetic media item') and gives a use case, making the tool's purpose clear. It does not compare itself to any sibling tools (e.g., create_bin, add_title), so it stops short of full differentiation.

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 offers an implied usage context ('useful for leader/calibration'), which hints at when to use it. However, there are no explicit when/when-not rules or named alternatives among the many sibling creation tools.

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

Deploy Server