{"id":"uk.co.theamateur/shoot-plan","slug":"uk-co-theamateur-shoot-plan","title":"Shoot Plan","description":"Practical filming plans for AI assistants, with tools to draft, check and export shot plans.","version":"0.1.1","publisher":{"kind":"domain","id":"theamateur.co.uk","label":"theamateur.co.uk","url":"https://theamateur.co.uk"},"website":"https://theamateur.co.uk/developers/shoot-plan/","repository":"","remotes":[{"type":"streamable-http","url":"https://theamateur.co.uk/mcp/shoot-plan"}],"packages":[],"published":"2026-10-26","updated":"2026-10-26","status":"online","auth":"","latency_ms":1183,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"shoot_plan_capabilities","title":"What Shoot Plan offers","description":"Return truthful Shoot Plan scope, availability, privacy and commercial state.","read_only":true},{"name":"shoot_plan_example","title":"See the example plan","description":"Return a synthetic example plan generated by the real planner, with its provenance.","read_only":true},{"name":"shoot_plan_quote","title":"Get a price","description":"Calculate a deterministic public quote from non-private project metadata. Do not send a script or brief.","read_only":true},{"name":"shoot_plan_create","title":"Create a plan","description":"Create a plan for an authenticated organisation after authoritative payment confirmation.","read_only":false},{"name":"shoot_plan_list","title":"List your plans","description":"List the authenticated organisation's Shoot Plans, most recently changed first, without returning private intake or full plan content. Archived plans are left out unless includeArchived is true. Each plan's taskId is the ID every other plan tool takes. Structured result: {plans:[...]}.","read_only":true},{"name":"shoot_plan_status","title":"Check a plan's progress","description":"Return a plan's status, version, whether its included revision is used, its customer-facing order reference, and progress (essential shots ticked, next shot, when the last tick was made). Read-only. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task prefix or orderReference also works. Connections see only their own live or owner-test plans.","read_only":true},{"name":"shoot_plan_get","title":"Open a plan","description":"Return a full plan: shots in filming order (priority must = essential), setup groups per location or visit, checklist, coverage risks, progress (item keys already ticked), progressSummary with counts, each tick's time and source (web, field or agent), and timeSummary when the plan has timing. Structured shots have a unique title and whole filming minutes (at least 1); older free-text shots omit bo","read_only":true},{"name":"shoot_plan_timing","title":"Compare planned and actual time","description":"Structured plans only (not older free-text plans). Compare planned and actual filming time between consecutive ticks in field mode. plannedSeconds is the planned time of those measured tick-to-tick steps, not the whole plan; planPlannedSeconds is the whole plan's planned shot work when present. Read-only. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task prefix o","read_only":true},{"name":"shoot_plan_revise","title":"Use the included revision","description":"Use the plan's one included revision. This cannot be undone and uses up that revision, so call shoot_plan_revision_preview first and confirm with the person. For structured plans, change filming time or transfer time (constraintUpdates.availableMinutes, locationTransferMinutes), framing, or structuredChanges. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task pref","read_only":false},{"name":"shoot_plan_revision_preview","title":"Preview a revision","description":"Structured plans only; older free-text plans cannot be previewed. Preview a revision without using it: what would change, which checked shots would be cleared, and whether it still fits. For example constraintUpdates.availableMinutes: 30 answers \"what if I only had 30 minutes?\". Never uses the included revision. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task p","read_only":true},{"name":"shoot_plan_progress_sync","title":"Tick off shots","description":"Tick or untick shots and checklist items. Each op: itemKey \"shot:<shotId>\" or \"check:<itemId>\" from shoot_plan_get, basePlanVersion = the plan's version, a new random UUID v4 as opId, state \"complete\" or \"incomplete\". Retry-safe: resending the same opId does nothing twice. An op made against an older basePlanVersion still applies when that item is unchanged in the current version; otherwise its re","read_only":false},{"name":"shoot_plan_check","title":"Check a shot plan will cut together","description":"Checks whether a shot plan will cut together before you film or generate it. It looks for crossed lines of action, mismatched eyelines, missing reactions, speakers who are never on screen, missing geography, jump cuts, travel direction, and props that change with no cause. It returns evidence from the plan and fixes it has already tested. The check is instant, and no AI model runs. It checks editi","read_only":true},{"name":"shoot_plan_missing_details","title":"List what a shot plan is missing","description":"Lists the questions to put to the person who knows the film, so that more of the plan can be checked. Each question uses the plan's own names, says which paths in the plan the answer fills in and which checks it unlocks, and says whether it blocks the assessment of a scene. Do not invent an answer to silence a question: when the honest answer is none, say so in the plan with a `none` declaration (","read_only":true},{"name":"shoot_plan_apply_fix","title":"Apply one tested fix to a shot plan","description":"Applies one fix, taken from a shoot_plan_check result, to a plan and checks the revised plan again. Some fixes trade one thing for another (each says its trade_off): tell your human before applying one that does. Input: plan; finding_id and fix_id (a finding's id, and the id of one of its suggestions, both from shoot_plan_check); and optionally findings, the check result you already have, which sa","read_only":true},{"name":"shoot_plan_format","title":"How to write a plan the checks can read","description":"Returns what you need to write or repair a plan that the checks can read: links to the JSON Schemas, the shortest valid plan, a worked example of a two-person scene that the checks find nothing wrong with, and a summary of the details that switch each check on (which is why a thin plan comes back \"not assessed\"). Call it first if you are about to write a plan. Input: none. Output: {schemas, smalle","read_only":true},{"name":"shoot_plan_fit_to_budget","title":"Cut a shot plan down to what the shoot can afford","description":"Cuts a plan down to what the shoot can afford, without dropping a shot marked `must`: it takes out the least necessary shots one at a time, re-checking the plan after each, and tells you what each cut costs. Input: plan, and constraints: max_shots (the most shots the cut may need) and/or max_setups (the most camera set-ups; shots sharing a set-up count once). The engine refuses any other limit and","read_only":true},{"name":"shoot_plan_shot_list","title":"Make a shot list from a plan","description":"Turns a plan into a shot list a crew can work from. Input: plan; format, \"json\" (default, dpl.shot-list/1) or \"markdown\"; vocabulary, an optional industry vocabulary for camera terms (for example \"movielabs@1.0\"). Output: the shot list, or {format:\"markdown\", markdown}. No AI model runs. We don't keep the plan. Needs an agent key from a Shoot Plan account, and is free up to 3 projects a month. A p","read_only":true},{"name":"shoot_plan_export_for_generation","title":"Prepare a plan for image or video generation","description":"Prepares a plan for generating its pictures with a generator of your own: it returns the editorial intent of the film (eil.intent/1) and one generation brief per shot (eil.generation-briefs/1). We run no generator and receive no media: you give the briefs to your own. Input: plan; optional sequence and sequence_revision (names for the sequence the intent describes), visual_family (a term for the k","read_only":true},{"name":"shoot_plan_draft_start","title":"Start drafting a shot plan from a brief","description":"Starts a shot plan for you to write: from a short brief it returns a valid skeleton plan (the places to write start with TODO), the layers to write it in, shot-pattern recipes for common kinds of scene, and the first thing to do. The loop is: you write the plan, we check it. We write none of the film and no AI model runs. The brief is sent to us only to build the skeleton, and we don't keep it. In","read_only":true},{"name":"shoot_plan_draft_from_script","title":"Start a shot plan from a screenplay","description":"Import a Fountain, Final Draft .fdx or plain-text screenplay into a valid starting plan with scenes, characters, places and lines. No AI model runs. Input: script as text; optionally as (fountain, fdx or text), otherwise detected from the content. Output: dpl.draft/1 with plan, layers and next_tool. Keep the plan, write the missing details, then follow next_tool. We don't keep the script. We log a","read_only":true},{"name":"shoot_plan_devices_suggest","title":"Suggest devices for a scene opening or cut","description":"List devices that could fit a scene opening, a shot or a join, best first, with reasons, missing details and when to use or avoid each. Candidates only: you choose; the plan is unchanged. No AI model runs. Input: plan (dpl.plan/1), exactly one of scene (id), shot (id) or join (two consecutive shot ids, a list or comma-separated text); optionally purpose (what the device should do). Output: dpl.dev","read_only":true},{"name":"shoot_plan_draft_next","title":"What to write next in a shot plan draft","description":"Says where a draft stands and the one next thing to do, so you can write a plan layer by layer and have each layer checked as you go. It reads the plan you send and never changes it. It returns the layer you have reached, what that layer still lacks as exact plan paths, the questions to put to your human (answer \"none\" in the plan when none is the honest answer; never invent a detail), the open fi","read_only":true},{"name":"shoot_plan_draft_gate","title":"Is the draft ready to shoot?","description":"The final check on a drafted plan: is it finished and ready to shoot? It returns ready or not ready, with a record of what was checked and what was not. A plan that does not pass gets a normal answer, not an error: the reasons are the next actions, each with its plan path and a fix. A pass is the result to show your human. It holds the plan to the format and to editing readiness, not to taste. No ","read_only":true},{"name":"shoot_plan_validate_takes","title":"Check a take log against its plan","description":"Checks a log of takes against the plan it was shot from, before you rely on it. It finds shots that are not in the plan, take numbers used twice, one op_id used for two different takes, file names written as paths, and a log made for another film or another revision of the plan. Each problem has a path into the log and a fix. A log with errors is a normal answer, not an error. The log is text abou","read_only":true},{"name":"shoot_plan_merge_takes","title":"Join two take logs into one","description":"Joins two take logs for the same film into one, for when two phones, an AI assistant and a script supervisor each kept a log while offline. Joining is by op_id, so a take that is in both logs counts once and merging again changes nothing. Where two logs hold different takes under one op_id, only one is kept and the clash is counted, with a fix: give one of them an op_id of its own. The tools take ","read_only":true},{"name":"shoot_plan_coverage_status","title":"Did we get it? What is covered and what is left","description":"Answers \"did we get it?\" before the crew leaves a location: from the plan and the take log it says which must-have shots have no good take, which reactions or cutaways the edit will need are still missing, what must match on the next set-up, and whether room tone was recorded. A \"hold\" verdict is not yet a decision, so it does not count as covered and is asked about. The tools take text only, neve","read_only":true},{"name":"shoot_plan_edit_guide","title":"A guide for the editor, from the plan and the takes","description":"Writes the editing guide for a film, scene by scene: what each shot is for, where to cut and why, which cutaway or insert covers which jump or crossed line, the sound to lay, and each open finding as a note about what to do in the edit. With a take log it also says which take stands for each shot and marks shots that have no usable take; without one it works from the plan alone. The tools take tex","read_only":true},{"name":"shoot_plan_export_edit","title":"Export the chosen takes as an edit for your editing software","description":"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","read_only":true},{"name":"shoot_plan_call_sheet","title":"Make a call sheet from a plan","description":"Makes the call sheet for a shoot from a plan's schedule: for the whole schedule, or for one shoot day, who is called, where and when, with the set-ups in order. A plan with no schedule has no times, and the call sheet says so rather than inventing any. Input: plan, a dpl.plan/1 object that validates; optionally day, the id of one day in the plan's schedule (a day the plan does not have is refused,","read_only":true},{"name":"shoot_plan_shoot_pack","title":"Make the shoot-day pack from a plan","description":"Makes the pack to take on the shoot day: the call sheet with, for each scene, its shots, the action, the look and the sound notes. Use it when the crew needs one document to work from; use shoot_plan_call_sheet when only the times and people are wanted. Input: plan, a dpl.plan/1 object that validates; optionally day, the id of one day in the plan's schedule (a day the plan does not have is refused","read_only":true},{"name":"shoot_plan_summary","title":"A short account of a plan, for when context is short","description":"Gives a short account of a plan, about 300 words, so that you can pick the work up again without being sent the whole plan: the title, the planned runtime against the target, the counts of scenes, shots, characters and places, the thesis and journey, one line for each sequence and scene, the missing-details counts, and, if you pass the check result, the open findings by severity. Fetch it first wh","read_only":true},{"name":"shoot_plan_slice","title":"Cut a smaller plan out of a big one","description":"Cuts out part of a plan, so that you can send a smaller plan when your context is short: the scenes, the shots or the sequence you name, with everything they refer to (characters, places, props, sound and the rest) and their times unchanged. The slice is a valid plan of its own, so you can send it to shoot_plan_check, and it says which whole plan it was cut from (slice_of). It is for reading and e","read_only":true},{"name":"shoot_plan_diff","title":"What changed between two versions of a plan","description":"Says what changed between two versions of a plan, so that you can catch up from a few lines instead of reading both. It compares by id, not by position, so reordering changes nothing: it lists what was added, what was removed, what changed (with the old and new values), and an id that has gone while another has appeared with the same content, which may be a rename: only a person can say. With the ","read_only":true},{"name":"shoot_plan_record_decision","title":"Record a decision about a finding","description":"Records a decision about one finding from shoot_plan_check (accepted, overridden or wont_fix), with the reason and who decided, so that you do not raise it again next session. We keep nothing: the answer is the updated decision log, and you must keep it and send it back to shoot_plan_check as dispositions. A finding with a remembered decision then comes back closed, with the reason, for as long as","read_only":true},{"name":"shoot_plan_to_dpl","title":"Convert a Shoot Plan you have bought into a DPL plan","description":"Converts one of your organisation's purchased Shoot Plan plans into a dpl.plan/1 plan in the short-form profile, so you can pass it to shoot_plan_check. It is the same conversion dpl-eil's reference importer makes, and it is one way only. Input: planId (the plan's planId, spp_..., as shown inside shoot_plan_get) or taskId (the full taskId from shoot_plan_list); optionally dayStart (HH:MM, default ","read_only":true},{"name":"shoot_plan_allowance","title":"How many projects this account has left this month","description":"Says what this account has used and has left of its monthly project allowance, the date it starts again, and, when the limit is reached, how to carry on sooner. A project is identified by the plan's work id and title: the same id and title is one project, and changing either starts a new one. It counts when a tool that makes a finished document (shot list, generation briefs, call sheet, shoot-day ","read_only":true}],"server_info":{"name":"the-amateur-shoot-plan","version":"2026-10-01.v1"},"category":"health","tags":[],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-10-19","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/uk-co-theamateur-shoot-plan/"}