Shoot Plan

Export the chosen takes as an edit for your editing software

shoot_plan_export_edit

Read-only

Makes a first assembly edit from the plan and the take log, as a file your own editing software opens: OpenTimelineIO (otio), FCPXML (fcpxml), a CMX 3600 edit decision list (edl) or an ALE log (ale). It puts the chosen takes in story order, each as long as the plan's slot (a shot with no usable take is left as a gap and listed in the report), linked by your human's own file names so they relink to footage on their own drives. No media is uploaded to us and none comes back; no AI model runs. Input: plan; takes (a dpl.takes/1 log); format (otio, fcpxml, edl or ale); optionally fps (24, 25, 23.976 or 29.97, a number or text; 24 if left out), drop_frame (true or false), media_root (the folder the footage is in, for relinking) and sync_sound (true by default). Output: {format, media_type, file_name, content, report, more_files?}. Save content as file_name. report lists the files to relink, the gaps, any warnings and what the chosen format cannot carry; an EDL is one file for each track, so any further files are in more_files, in order. We don't keep the plan or the take log. Needs an agent key from a Shoot Plan account, and is free up to 3 projects a month. A project is identified by the plan's work id and title; it counts when this tool first makes a finished document for it that month. shoot_plan_allowance says what is left. Over the limit it answers ALLOWANCE_REACHED: do not retry, a new key will not help, tell your human. A fair-use limit also applies: up to 20 finished-document calls for any one project and 60 for the account each month. To count projects we keep, against your account, a one-way fingerprint (hash) of the project's id and title, the month, how many finished documents were made and when, for 13 months after the end of that month. Plans up to 8 MB and 120 calls a minute (5,000 a day).

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": {
      "plan": "<plan>",
      "takes": "<takes>",
      "format": "<format>"
    },
    "name": "shoot_plan_export_edit"
  }
}

Input Schema

Name	Required	Description
`fps`	No	Frame rate: 24, 25, 23.976 or 29.97 (a number or text). Optional.
`plan`	Yes	The plan itself: a dpl.plan/1 JSON object (not text inside a string). Call shoot_plan_format for the schema links and an example.
`takes`	Yes	The take log: a dpl.takes/1 JSON object, {format, work_id, takes: [...]}. Each take has op_id, shot (the plan's shot id), kind and verdict; file names and timecodes are optional. A take log holds text about recordings: the tools take no video or audio.
`format`	Yes	otio, fcpxml, edl or ale.
`drop_frame`	No	Optional: drop-frame timecode. Default false.
`media_root`	No	Optional: the folder the footage is in, for relinking.
`sync_sound`	No	Optional: include sync sound where the log has it. Default true.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only cover read-only and closed-world, and the description adds substantial context beyond them: no media is uploaded or returned, no model runs, the plan and take log are not retained, a hashed project fingerprint is kept for 13 months, and billing/quota mechanics with a specific error code. It also discloses output quirks an agent must handle, such as an EDL producing one file per track with extras in more_files and unusable shots becoming gaps.

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?

It is front-loaded with the purpose, then inputs, then the output shape, then limits, and nearly every sentence carries operational information (quota rules, retention, format limitations). The weakness is density: the quota, retention and rate-limit material runs together as one undifferentiated block, which makes the critical ALLOWANCE_REACHED instruction easy to miss.

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

Completeness5/5

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

For a tool with nested objects, an output schema, and metered billing, the description covers what an agent most needs: required inputs, format choices, defaults, the meaning of report and more_files, and how to behave on quota failure. Nothing material for a correct first call is missing.

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 coverage is 100%, so the schema already documents all seven parameters including defaults for fps, drop_frame and sync_sound. The description restates the format list, the fps default of 24, sync_sound defaulting to true and media_root's relinking purpose, but adds no syntax or edge-case guidance beyond the schema. Baseline 3 applies where the schema carries the weight.

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?

It states a specific verb and artifact: 'Makes a first assembly edit from the plan and the take log' into otio, fcpxml, edl or ale. The operation is unambiguous, but the description never contrasts itself with the closest siblings (shoot_plan_export_for_generation, shoot_plan_edit_guide), so an agent must infer the boundary from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the alternative mechanism ('shoot_plan_allowance says what is left') and gives an explicit when-not rule: on ALLOWANCE_REACHED, 'do not retry, a new key will not help, tell your human.' It also sets the operating envelope (fair-use caps, 120 calls/minute, 5,000 a day), so the agent knows the conditions under which calling is inappropriate.

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

All Shoot Plan tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?