actorsOfTheCompany
ChatGPTLists all actors and extras from the company's cast database, including union, agency and agent information as well as physical and wardrobe measurements. projects shows the projects an actor is assigned to; shootingBlocks and episodes reference the organisation units also used by the shooting schedules. To see which character an actor portrays in a project, use charactersOfAProject and follow its depiction references (com.yamdu.app.actor.{id}). Food preferences, allergies and ethnicity are available only to API keys carrying the sensitive-data permission; OAuth-connected responses never contain them. Contact details, addresses and the date of birth are included only when the credentials may read sensitive personal data; over OAuth the company's MCP setting and the user's project right must both allow it. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
aggregatedTimeCardTotalsOfAProject
ChatGPTTime card totals of a project (projectId from projectsOfTheCompany), rolled up per weekly batch. groupBy: omitted = one grand total, else person, week, month, person,week or person,month (week+month invalid); weeks follow the project's weekStartDay. The weekly minimum-hours guarantee only applies to whole weeks inside the range, so month buckets and cut weeks report raw sums; totals covers the full range; the groups buckets are subsets of it, not summands. Filters: start/end (work day, inclusive), userId or actorId (not both; see crewListOfAProject, actorsOfTheCompany), search, workType, status - the last two take comma lists, ! excludes. Declined time cards count in timecardCount/byStatus but are never summed. Hidden values are empty, never 0. The *ForTimeAccount penalties break down timeAccount.supplement. An absent value in this payload is meaningful rather than unknown. Each metric block carries a calculationState: "aggregated" means the figure was summed from the underlying time cards, while "hidden" means the caller's permissions do not expose that metric, which is a permission boundary rather than a value of zero. blockedTimecardCount states how many time cards in the bucket could not be fully calculated; while it is greater than zero the aggregated figures are a lower bound. A bucket whose time cards come from labor agreements with more than one rate currency leaves currency and every monetary field empty - salary, penalty amounts, per diems, kit fee and the time account supplement - because amounts in different currencies cannot be added up; hours, counts and the time account variance stay populated, and the calculationState remains "aggregated". A missing currency next to an "aggregated" block is therefore a statement about the currency and never a permission boundary: with the monetary fields empty as well it is such a mixed-currency bucket, with amounts present the contributing labor agreements carry no rate currency. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
allBudgetScenariosOfAProject
ChatGPTLists all budgeting scenarios of the selected project (get the projectId from projectsOfTheCompany), estimates and actuals in one flat list. Use it to find the scenario to inspect: type tells estimate from actual, status reports the workflow state (draft, inProgress, final, locked), and grandTotal with currency gives the bottom line without loading the tree. Filter with type to compare like with like. Pass the returned id to specificBudgetScenario for the full topsheet/subcategory/entry breakdown. Requires the budgeting feature on the company's subscription. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
allCallSheetsOfAProject
ChatGPTLists all call sheets of the selected project (get the projectId from projectsOfTheCompany). Use it to find the call sheet for a specific day: each entry contains the date, the linked shooting day (shootingDayId and shootingDayNumber, matching the shooting schedule days and the OMC shoot day contexts), status information (isFinal, hasBeenSent, isInThePast) and the locations of the day. Pass the returned id to specificCallSheet for the full call sheet. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
allProductionCalendarsOfAProject
ChatGPTLists all production calendar versions of the selected project (get the projectId from projectsOfTheCompany). A production calendar holds the high-level production timeline: phases, steps and milestones such as prep, shoot and post. It is not the day-by-day shooting plan, which is provided by allShootingSchedulesOfAProject. isActiveVersion marks the active calendar; pass the returned id to specificProductionCalendar for the production steps with dates and dependencies. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
allShootingSchedulesOfAProject
ChatGPTLists all shooting schedule versions of the selected project (get the projectId from projectsOfTheCompany). Use it to find the schedule version to inspect: isActiveVersion marks the currently active plan, and start, numberOfShootingdays, hasBeenShot and status summarize each version. Pass the returned id to specificShootingSchedule for the full day-by-day plan. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
charactersOfAProject
ChatGPTLists the characters (roles) of the selected project as OMC Character entities, identified by com.yamdu.app.role.{id}. Each character contains the character name and description, Depiction linking to the actor portraying the character (com.yamdu.app.actor.{id}, see participantsOfAProject and actorsOfTheCompany), and Context[].featuresIn.NarrativeScene listing the narrative scenes the character appears in (com.yamdu.app.scene.{id}, see narrativeScenesOfAProject). Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
creativeWorksOfTheCompany
ChatGPTLists the projects these credentials can reach as OMC CreativeWork entities. This is the entry point of the OMC listings: their creativeWorkIdentifiers parameter takes episode ones only; others use creativeWorkIdentifier. A non-episodic project yields one entry with creativeWorkTypecreativeWork and the identifier com.yamdu.app.project.{id}; an episodic project yields a season entry plus one episode entry per episode (com.yamdu.app.episode.{id}), cross-linked through Episode and Season. title.workingTitle holds the name, customData.yamdu.shootingBlock the shooting block of an episode. See projectsOfTheCompany for the full production data of a project. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
crewListOfAProject
ChatGPTReturns the crew list of the selected project without open positions (get the projectId from projectsOfTheCompany). The crew list includes both users and external contacts assigned to the project; id values are only unique within an entityType ("user" or "externalcontact"). Each entry contains the person's name and their positions and departments. Sensitive personal information (personalInfo with contact, HR and payroll details) is only included when the caller's credentials grant the necessary permissions; identity documents, visa and work permit, tax, social security, health insurance, pension fund, bank and disability details are additionally limited to API keys and never part of OAuth-connected responses. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
crossEntitySearchOverTheScriptBreakdownOfAProject
ChatGPTSearches the script breakdown of the selected project in one call across characters, narrative locations/sets, wardrobes, props, scene attributes (effects, stunts, narrative audio) and the narrative scenes themselves. Entities match when their name contains the search term; scenes match on scene number, description or note. Each hit carries its identifier and entity type, narrativeScenes (the scenes it appears in, with scene number) and shootDays - the shoot days of the active shooting schedule those scenes are scheduled on (com.yamdu.app.shootDayContext.{id}, with number and date), so continuity questions such as "on which shoot days does this costume appear?" are answered in one request. Use entityTypes to restrict the search to specific entity types. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
effectsOfAProject
ChatGPTLists the visual and special effects of the selected project as OMC Effect entities, identified by com.yamdu.app.sceneattribute.{id}. Effects are the scene attributes of the project's visual/special effects categories; effectType is visualEffect or specialEffect. Each entry contains its name, its description (the breakdown note) and Context[].featuresIn.NarrativeScene referencing the narrative scenes the effect appears in (com.yamdu.app.scene.{id}, see narrativeScenesOfAProject). Stunts are returned by specialActionsOfAProject, audio items by narrativeAudioItemsOfAProject, all remaining scene attributes and props by narrativeObjectsAndSceneAttributesOfAProject. To find the shoot days an effect is needed on, use crossEntitySearchOverTheScriptBreakdownOfAProject. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
laborAgreementsOfAProject
ChatGPTReturns the labor agreements (in the Yamdu UI also called time card settings) of the selected project (get projectId from projectsOfTheCompany): one entry per crew member or cast member, describing the rules their time cards are calculated with. Each entry contains the linked labor agreement template with its union and union local, rates, weekStructure, the regular-day hour bands (overtimeBands), weeklyOvertime thresholds, meals (break and meal penalty rules), nightPremium levels, restPeriod, perDiems, kitFee, mileage, car allowance and the holidayRegion. Filter by person (userId from crewListOfAProject or actorId from actorsOfTheCompany, not both) or search on the person name. Use timeCardsOfAProject for the actual work days these rules are applied to. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
locationsOfTheCompany
ChatGPTLists the physical locations from the company's location database: real-world places such as shooting locations, offices or studios, including address, latitude/longitude, timezone UTC offset (tzUtcOffset), contact details and notes. projects shows which projects use a location. Not to be confused with the narrative locations (story places/sets of a script), which are returned by narrativeLocationsOfAProject. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
narrativeAudioItemsOfAProject
ChatGPTLists the narrative audio items of the selected project as OMC NarrativeAudio entities, identified by com.yamdu.app.sceneattribute.{id}. They are the scene attributes of the project's audio and sound categories; narrativeType is narrativeAudio or narrativeSoundEffect. Each entry contains its name, its description (the breakdown note) and Context[].featuresIn.NarrativeScene referencing the narrative scenes it appears in (com.yamdu.app.scene.{id}, see narrativeScenesOfAProject). Effects are returned by effectsOfAProject, stunts by specialActionsOfAProject, all remaining scene attributes and props by narrativeObjectsAndSceneAttributesOfAProject. To find the shoot days an audio item is needed on, use crossEntitySearchOverTheScriptBreakdownOfAProject. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
narrativeLocationsOfAProject
ChatGPTLists the narrative locations (story places/sets, e.g. "JOHN'S APARTMENT") of the selected project as OMC NarrativeLocation entities, identified by com.yamdu.app.set.{id}. Context[].featuresIn.NarrativeScene references the narrative scenes playing at the location, including the scene's name and description (com.yamdu.app.scene.{id}, see narrativeScenesOfAProject). These are story places from the script; the company's real-world locations are returned by locationsOfTheCompany instead. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
narrativeObjectsAndSceneAttributesOfAProject
ChatGPTLists the props (com.yamdu.app.scriptprop.{id}) and scene attributes (com.yamdu.app.sceneattribute.{id}) of the selected project as OMC NarrativeObject entities. Each entry contains its name and description and Context[].featuresIn.NarrativeScene referencing the narrative scenes the object appears in (com.yamdu.app.scene.{id}, see narrativeScenesOfAProject). For continuity questions such as when a prop is on set, follow the scene references to productionScenesOfAProject and from there to the shoot day contexts (shootingDaysOfAProject). Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
narrativeScenesOfAProject
ChatGPTLists the script scenes of the selected project as OMC NarrativeScene entities, identified by com.yamdu.app.scene.{id}. Each scene contains the scene number, slugline (INT/EXT, time of day), name and description, and Context[].features referencing the characters, narrative location, narrative objects, special actions and effects appearing in the scene. Narrative scenes do not link forward to shooting days: to find out when a scene is scheduled, look up the production scene with the same trailing id via productionScenesOfAProject and follow its shootDayContext references. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
narrativeWardrobesOfAProject
ChatGPTLists the wardrobe items (costumes) of the selected project as OMC NarrativeWardrobe entities. Each item contains its name and description, Context[].neededBy.Character referencing the character wearing it (com.yamdu.app.role.{id}, see charactersOfAProject) and Context[].featuresIn.NarrativeScene referencing the narrative scenes it appears in (com.yamdu.app.scene.{id}, see narrativeScenesOfAProject). For continuity questions such as when a costume is on set, follow the scene references to productionScenesOfAProject and from there to the shoot day contexts (shootingDaysOfAProject). Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
participantsOfAProject
ChatGPTLists the participants of the selected project as OMC Participant entities: the cast members (participantFC.functionalTypeactor, identified by com.yamdu.app.actor.{id}, see actorsOfTheCompany) and the project's production units (functionalTypeproductionUnit, com.yamdu.app.productionUnit.{id}), which the shoot day contexts reference as has.Participant (see shootingDaysOfAProject). A cast participant carries the person's name in ParticipantSC.personName.firstGivenName plus an optional description and gender; contact email and phone are only included when the credentials may read sensitive personal data. Use charactersOfAProject to see which character an actor portrays. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
productionLocationsOfAProject
ChatGPTLists the real-world shooting locations of the selected project as OMC ProductionLocation entities, identified by com.yamdu.app.location.{id} - the same records the company location database returns via locationsOfTheCompany (with timezone, contacts and tags). Each entry contains its name, its description (the location note), locationTypeshooting and a nested Location object with address (street, postal code, country) and coordinates (latitude, longitude). These are physical places; the story places/sets of the script are returned by narrativeLocationsOfAProject. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
productionScenesOfAProject
ChatGPTLists the production scenes (and shots, if a scene is broken down into shots) of the selected project, the bridge from script to shooting plan. A production scene shares its trailing id with the corresponding narrative scene and references it via Context[].for.NarrativeScene; additional Context entries carry one com.yamdu.app.shootDayContext.{id} reference per shooting day the scene is scheduled on in the active Yamdu shooting plan (see shootingDaysOfAProject). Scheduled scenes and shots expose production metadata such as scheduled time, shot size, shot type, movement, equipment, VFX, camera, lens, framerate, sound, lighting, location and setup ID as customData.yamdu.customFields; each custom field contains a stable key, a localized label and the field value. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
projectsOfTheCompany
ChatGPTLists the projects (productions) these credentials can reach: with an API key the projects of its company, with an OAuth token those of every company that enabled MCP for the user. This is the entry point of the API: the returned id is the project identifier expected by all project-scoped endpoints (the projectId parameter of allShootingSchedulesOfAProject, allProductionCalendarsOfAProject, allCallSheetsOfAProject, crewListOfAProject and allBudgetScenariosOfAProject, and the project parameter of the OMC tools), and it also forms the OMC Creative Work identifier com.yamdu.app.project.{id}. Each project additionally contains its name, short name, creation date, status tags and general production data such as production company, production type and language. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
shootingDaysOfAProject
ChatGPTLists the shooting days of the active Yamdu shooting plan of the selected project as OMC Context objects with contextType "shootDay", identified by com.yamdu.app.shootDayContext.{id} (the same shooting day id used by the call sheets and shooting schedule days). Each Context contains the shoot day number and date (contextProperties.shootDay and contextProperties.shootDate in yyyy-MM-dd format), the owning project (for.CreativeWork), the production scenes scheduled for that day (has.ProductionScene, see productionScenesOfAProject) and optionally the assigned production unit (has.Participant). Resolves what is shot on which day. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
specialActionsOfAProject
ChatGPTLists the stunts of the selected project as OMC SpecialAction entities, identified by com.yamdu.app.sceneattribute.{id}. They are the scene attributes of the project's stunt categories; specialActionType is stunt. Each entry contains its name, its description (the breakdown note) and Context[].featuresIn.NarrativeScene referencing the narrative scenes it appears in (com.yamdu.app.scene.{id}, see narrativeScenesOfAProject). Effects are returned by effectsOfAProject, audio items by narrativeAudioItemsOfAProject, all remaining scene attributes and props by narrativeObjectsAndSceneAttributesOfAProject. To find the shoot days a stunt is needed on, use crossEntitySearchOverTheScriptBreakdownOfAProject. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
specificBudgetScenario
ChatGPTReturns one budgeting scenario with its complete three-level breakdown: topsheets (account groups) contain subcategories, which contain the individual entries with quantity, unit, rate, multiplier, subtotal (pre-fringe), fringeTotal and total. Every level carries its own accountNumber and totals. entries[].includedInTotals is false for entries excluded from the totals (in-kind, deferred, or in a switched-off group). entries[].linkedItem points at the linked cast/location/prop/contact record. grandTotal equals the sum of all topsheets[].total plus all contractualCharges[].total; subtotalRows are display bands re-partitioning the same topsheets (see topsheetIds), so they restate amounts that grandTotal already contains. Get scenario ids from allBudgetScenariosOfAProject. Needs the budgeting add-on. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
specificCallSheet
ChatGPTReturns one call sheet with the complete plan of the day: the covered shooting day(s), the scene schedule (schedule[].item.id is the scene identifier matching the OMC narrative scenes), individual call times for cast (pick-up, arrival, make-up, costume, ready-to-shoot) and crew, the general crew call, locations, events and weather. Use this to answer questions like when someone is expected on set on a given day. Get call sheet ids from allCallSheetsOfAProject. Elements of type weather and hospital report their stored content as the typed objects elements[].weather and elements[].hospital instead of as raw text in elements[].content. The content of the rich-text element types and signature is the stored HTML of the call sheet, HTML entities included. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
specificProductionCalendar
ChatGPTReturns one production calendar version with all its production steps: each step has a name, the production phase it belongs to (productionPhase), isMilestone, start and end (all-day calendar dates carried in a UTC timestamp whose time of day is an artefact of when the step was positioned and is often not 00:00, so only the date part is meaningful), whether weekends and holidays are excluded from its duration, and its dependencies to other steps (dependsOn, dependingSteps, both production step ids). This is the high-level production timeline (prep, shoot, post), not the day-by-day shooting plan - that one is returned by specificShootingSchedule. Get calendar ids from allProductionCalendarsOfAProject. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
specificShootingSchedule
ChatGPTReturns one shooting schedule version with its full day-by-day plan: shooting phases (each with start/end, assigned unit and timeZone) contain shooting days, which contain the scheduled scene entries. shootingDays[].id is the shooting day identifier also used by call sheets (shootingDayId) and by the OMC shoot day contexts (com.yamdu.app.shootDayContext.{id}). schedule[].item.id of a day is the scene identifier matching the OMC narrative scenes (com.yamdu.app.scene.{id}). Get schedule ids from allShootingSchedulesOfAProject. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
timeCardsOfAProject
ChatGPTDaily time cards of a project (get projectId from projectsOfTheCompany): one row per person and work day, grouped into person (crew userId from crewListOfAProject, cast actorId from actorsOfTheCompany), workDay, times (local wall clock of times.timezone), meals, drives, hours, penalties, timeAccount, totals, perks, rerates, approval (status plus all five stages) and notes. Filter by start/end, userId or actorId (not both), search on the person name, workType and status - the last two also take comma-separated lists, or a ! prefix to exclude, e.g. workType=!off for every day except off days. Payroll values the caller may not see are empty, depending on their time card permission and the project's visibility settings. See laborAgreementsOfAProject for the rules behind the numbers. An absent value in this payload is meaningful rather than unknown, and what it means depends on the field. The hours, totals, penalties and timeAccount blocks each carry a calculationState: with "calculated" an empty value means none or zero, "blocked" means the figure could not be computed and blockedBy names the reason, and "notApplicable" means the block does not apply to that day. Elsewhere: a meal with neither start nor end was never taken, while a start without an end is a break that was never closed; empty drives, nonDeductibleBreak, notes or perk amounts mean nothing was logged, written or granted for that entry; an approval stage without a status has not been reached yet, because the workflow is sequential; an empty comments[].updatedAt means the comment was never edited; and empty workDay.workLocation fields mean no location was recorded. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
whoAmI
ChatGPTReturns who the current credentials belong to and what they can reach, so an AI client can tell the user which account and company it is working with. Contains the authentication method (api_key or oauth), the granted API scopes, and the companies these credentials can be used for (id, name and the scopes the company's own settings allow there). For an OAuth token it also returns the Yamdu user (id, name, email); for an API key the key id, its name and whether it may reach all projects of the company. companiesWithoutMcpAccess counts further companies of the user without MCP: if above 0, this result is narrower than what the user sees in Yamdu, so an absence here is not evidence that the data does not exist. Requires no scope: any valid API key or access token may call it. Response id values are internal identifiers accepted as input by follow-up tool calls. webUrl (or the identifier url) fields are the public links to the records.
actorsOfTheCompany
ClaudeaggregatedTimeCardTotalsOfAProject
ClaudeallBudgetScenariosOfAProject
ClaudeallCallSheetsOfAProject
ClaudeallProductionCalendarsOfAProject
ClaudeallShootingSchedulesOfAProject
ClaudecharactersOfAProject
ClaudecreativeWorksOfTheCompany
ClaudecrewListOfAProject
ClaudecrossEntitySearchOverTheScriptBreakdownOfAProject
ClaudeeffectsOfAProject
ClaudelaborAgreementsOfAProject
ClaudelocationsOfTheCompany
ClaudenarrativeAudioItemsOfAProject
ClaudenarrativeLocationsOfAProject
ClaudenarrativeObjectsAndSceneAttributesOfAProject
ClaudenarrativeScenesOfAProject
ClaudenarrativeWardrobesOfAProject
ClaudeparticipantsOfAProject
ClaudeproductionLocationsOfAProject
ClaudeproductionScenesOfAProject
ClaudeprojectsOfTheCompany
ClaudeshootingDaysOfAProject
ClaudespecialActionsOfAProject
ClaudespecificBudgetScenario
ClaudespecificCallSheet
ClaudespecificProductionCalendar
ClaudespecificShootingSchedule
ClaudetimeCardsOfAProject
ClaudewhoAmI
Claude