Exportlab

Get the studio's public profile — display name, tagline, intro, bio, gear list and whether it is published. Use before suggesting improvements to the wording. Images, pricing and contact routing are summarised as counts and booleans rather than returned.

get_public_profile

Get client review comments for a video, with timecodes, resolution status and replies. This is the tool for 'what still needs changing in video X' — the output can be turned directly into an editing to-do list. Find videoIds with list_videos.

get_video_feedback

Add participants to a group-shoot gallery — e.g. from a staff list the user pastes in. Parse their file yourself and pass structured rows; ask which column is which if it is ambiguous. Maximum 200 per call; split longer lists. People already present with the same employee ID are skipped. Access codes are generated per person and are visible in Exportlab, never here.

import_group_shoot_people

List pre-production asset collections — the questionnaires and file requests sent to clients. Shows how many files and answers have come back. Use for 'what is still missing from the client before the shoot'. The share link is never returned: it grants upload access to the workspace. Point the user to the collection in Exportlab instead — do not construct a URL.

list_asset_collections

Shoots, calls, meetings, deadlines and deliveries in a date range. Defaults to the next 30 days. Meeting notes are never returned — only whether notes exist.

list_schedule_events

List clients in the workspace — company, contact person, location, tags, status and last contact date. Use for CRM questions such as which clients exist, who has not been contacted recently, or to find a clientId. Email addresses and phone numbers are never returned.

list_clients

List enquiries submitted through the public profile page, newest first — who wrote in and what they asked for. Use this to draft a reply or a quote. Email addresses and phone numbers are never returned: write the reply here, then send it from Exportlab, where the contact details already are.

list_contact_enquiries

List the contract templates available in this workspace — the studio's own plus the built-in ones for photo and video work. Each carries `variables`, the placeholders a draft can fill (client name, shoot date, fee). Call this before create_contract_draft to choose a template and learn its placeholders. The legal wording itself is not returned.

list_contract_templates

List contracts across projects with their signing state — sent, signed by the client, counter-signed, and when the signing link expires. Use for 'which contracts are still open' or 'where is my counter-signature missing'. Signing links are deliberately NEVER returned: whoever holds one can sign the contract as the client. If asked for one, explain that and point the user to the contract in the Exportlab project — do not guess or construct a URL.

list_contracts

List photo galleries — name, photo count, experience/mode, linked project or client, and `publicUrl`, the link to send a client. If `hasPin` is true the gallery is PIN-protected: the PIN is NEVER returned, so tell the user they must share it separately. If `hasPin` is false, anyone with the link can view the photos — say so when you hand the link over. Collaborative galleries also carry `collabUrl`, group shoots `checkinUrl`.

list_galleries

List guest-upload events (weddings, parties, corporate events) with upload counts, storage used, pass tier and last activity, plus `uploadUrl` — the guest link, the one printed on the event's QR card. Anyone with it can upload, so say that when sharing it. Guest email addresses are never returned.

list_upload_events

List the model release templates in this workspace, with the placeholders each one uses. Call before prepare_model_release.

list_model_release_templates

List workspace notifications, newest first — new feedback, uploads, contract activity and processing events. Use to catch up on what happened recently.

list_notifications

Which notes a project has, with their titles and lengths. The note text itself is deliberately not returned — it is what the studio wrote about a client for themselves. Use append_project_note to add one.

list_project_notes

List projects in the workspace — title, client, workflow phase and dates. Use this to answer questions about what the studio is working on, what is stalled, or to find a projectId for other tools. Optionally filter by client.

list_projects

List the proposals in this workspace, newest first. Pass projectId to narrow it to one project. Returns status, number, total-facing metadata and timestamps — not the document body, the recipient's address or the share link.

list_proposals

Open and waiting tasks in the workspace. Use this to answer what the studio still has to do, what is overdue, or what is blocked on a client. A task with status "waiting" carries who it is waiting on and since when. Task descriptions are not returned — only titles.

list_tasks

Time entries in a date range, defaulting to the last 30 days. Durations are in seconds. Use this to answer how long something took or where the week went.

list_time_entries

List videos — title, linked project, processing and review status, version count, and `reviewUrl`, the client review page. If `hasSharePin` is true a PIN is required to open it and is never returned — mention that. Use to find a videoId, or to answer which videos are awaiting client approval.

list_videos

Record that a task is blocked on somebody else — usually the client — with an optional date to chase it. Use this when the user says they have sent something and are waiting for a reply.

set_task_waiting

Post a progress update to a project's status page — the page the client already has a link to. Nothing is sent; the client sees it next time they look. Use it when the user says what has happened on a project. The status page must already be enabled in Exportlab.

post_status_update

Prepare a contract on a project as a DRAFT, filling in the template's placeholders. Nothing is sent: no email goes out, no recipient is set, and the client cannot see or sign it. The studio reviews the draft in Exportlab and sends it themselves — say so when you report back. Fill only placeholders the user actually gave you. A placeholder you leave empty becomes a field the client fills in when signing, which is the right outcome for anything unknown — never invent a fee, a date or a jurisdiction. Get templateId and the placeholder names from list_contract_templates.

create_contract_draft

Stage a model release on a project using one of the workspace's templates. It is left switched OFF: the signing page stays closed until the studio turns it on in Exportlab, so no one can sign in the meantime. Mention that final step when you report back.

prepare_model_release

Prepare a proposal on a project as a DRAFT. Nothing is sent: no proposal number is assigned, no client link is created and no email goes out. The studio reviews the draft in Exportlab and publishes it themselves — say so when you report back. A proposal always belongs to a project, because the project page is where it is shown. If the user has not named one, call list_projects and ask which it belongs to, or create_project first when the job is new — do not guess an id. A client is optional and not needed to send the proposal. Prices are integers in minor units: 1.400,00 EUR is 140000. Never pass a decimal. Take prices from search_service_catalog where possible and ask the user rather than inventing a figure. Mark a line `optional: true` for work the client can choose to add; those are excluded from the base total and the client ticks them on the proposal page. The totals in the response are recalculated by the server — report those, not any figure you worked out yourself.

create_proposal_draft

Mark a client review comment as done, or skipped with a reason. Use after get_video_feedback when the user says which points they have handled. The client's own words are never changed — only the state of the note.

resolve_video_feedback

List the studio's reusable services with their standard prices. Use this to build line items with the studio's real prices instead of inventing figures. Prices are in minor units: 140000 means 1.400,00 EUR.

search_service_catalog

Search across projects, clients, galleries and videos by name in one call. Use when the user mentions something by name and you do not know which module it lives in — 'find everything about BMW', 'where is the Müller shoot'. Returns matches grouped by type, with the ids AND public links other tools need — a gallery match already carries its `publicUrl`.

search_workspace

Begin tracking time against a project and category. There is exactly one timer per user: if one is already running this fails rather than switching, because reassigning tracked hours is not something to do on a guess. Stop the running one first if the user means to switch.

start_timer

Stop whatever timer is running and close it into a time entry. Stopping when nothing runs is not an error — it reports that nothing was running.

stop_timer

Update a client's CRM record — contact details, address, tags, notes, status, source. Only the fields you pass are changed. Billing identifiers cannot be changed here.

update_client

Rename a gallery, set its description, or link it to a client or project. Useful for tidying up in bulk — call it once per gallery. Photos, PIN, visibility and sharing are not touched.

update_gallery

Correct a participant's details or move them to a different shooting day — the corrections that always follow an import. Their access code and photos are untouched.

update_group_shoot_person

Replace the contents of an existing DRAFT proposal. Read it with get_proposal first and pass the `revision` you saw as expectedRevision — if someone edited it in the meantime the update is rejected rather than overwriting their work, and you should re-read and try again. This replaces the line items wholesale, so include every line you want the proposal to end up with, not just the changed ones. A published proposal cannot be updated.

update_proposal_draft

Background steps that failed in this workspace: preview images, video processing, signed contract PDFs, invoice documents, proposal PDFs, receipt text recognition and other background jobs. Each item has an errorCode, a user-safe errorMessage and whether it can be retried. Read-only: retrying happens in the Exportlab app (or with Labby there). Use it for "did anything fail?" or "why is X missing?".

list_failed_operations

Work that is slipping: overdue tasks, follow-ups whose date has arrived, deadlines with open work behind them, meetings finished without notes. Every item carries a structured `reason` — answer with those facts rather than inventing an explanation. This is the tool for "what needs my attention today?".

get_needs_attention