Loopsii

Read the signed-in user's own account settings: name, workspace slug, timezone, currency, hourly rate, and the business identity printed on their documents (business name, address, VAT and registration numbers). Use it when you need the user's currency or rate for a calculation, or their business identity for a document. Bank details are never returned.

get_profile

Read one project in full — stage, client, start date, deadline, price, hourly rate and description. A null hourlyRate means the project bills at the default rate from get_profile. Use it before answering questions about a specific project or before updating it.

get_project

Read one screen recording: metadata, its summary and transcript, plus the public watch URL when sharing is on. Use it to answer questions about what a recording shows. The transcript comes back 30000 characters at a time: while transcriptNextOffset is not null, call again with transcript_offset set to it to read on.

get_recording

Read one task in full — description, status, priority, project, milestone, due date, where it came from and its comments, newest first. Use it before quoting a task detail back to the user or before updating one. The task can be a UUID, an id prefix, or any part of its title.

get_task

List every client with contact and billing details; archived clients are included and marked isArchived. Use it to answer "who are my clients", or to find the client id a project or invoice question needs.

list_clients

List the documents in the workspace, newest first — id, title, kind, project and when each was last touched. Use it to see what the user has written, or to find the document another document tool needs. Filter by project and by kind: a plain doc, or an estimate, proposal or agreement.

list_documents

List recent meetings, newest first — id, title, platform, date and duration. Use it to find the meeting the user means before calling get_meeting.

list_meetings

List the people the user has met with, from meeting attendance — name, email, how many meetings and the most recent one. Use it to answer "who have I been meeting" or to check when someone last came up.

list_people

List projects with their id, name, slug and whether each is archived. Archived projects are left out unless include_archived is true — set it when the user asks about old, finished or archived work. Use it to see what the user is working on, or to get the id a project tool needs.

list_projects

List recent screen recordings, newest first — id, title, date, duration, processing status and views. Use it to find the recording the user means before calling get_recording.

list_recordings

List tasks, newest first — id, title, status, priority, project and due date. Use it to answer "what is on my list" or "what is left on the Acme project", and to find the task another task tool needs. Filter by project (a name, an id, or "none" for tasks filed under no project) and by status.

list_tasks

List logged time entries over a date window with their durations, descriptions and projects. Use it to answer "how much did I work on X" or to summarise a day, week or month.

list_time_entries

Search the whole Loopsii workspace at once — projects, clients, tasks, documents, invoices and meetings. Use this first whenever the user names something ("the Acme brief", "that invoice") and you do not already know its id; it returns titles, subtitles and absolute app URLs. Narrow it with type, project, client or since when the user scopes the question ("meetings about pricing in the Acme project since June"); with a filter set the query may be left out.

search

Start the time tracking timer, optionally against a project. Any timer already running is stopped and logged first. Use it when the user says they are starting work on something.

timer_start

Stop the running timer and log the entry, reporting how long it ran. Use it when the user says they are done with what they were tracking.

timer_stop

Check whether a time tracking timer is running right now, and for how long. Use it before starting or stopping a timer, and whenever the user asks what they are working on.

timer_status

Change contact or billing fields on an existing client, or archive and restore it — archiving a client archives its projects with it. Pass only what changes; null clears a field. Use it when the user gives you a new address, VAT number or billing email.

update_client

Rename a document or rewrite its body. The content you pass REPLACES the entire document — call get_document first, edit the markdown it hands back, and send the whole result, or everything you left out is deleted. Keep ```estimate fences and "> [!NOTE]" callouts exactly as they came unless the user actually wants them changed. Pass only what changes. Show the returned url to the user — it opens the document in Loopsii.

update_document

Rename a meeting or file it under a project. Pass only what changes. Use it when the user says which project a call belonged to, or wants a clearer title than the generated one.

update_meeting

Change the signed-in user's own settings — display name, timezone, currency, hourly rate, and the business identity that appears on their documents (business name, address, VAT and registration numbers). Pass only what changes; null clears a nullable field. Email, workspace slug, avatar and bank details cannot be changed here.

update_profile

Change fields on an existing project — rename it, move its stage, assign a client, set dates, the estimated price or its own hourly rate, archive or restore it. Pass only what changes; null clears a nullable field. Renaming regenerates the slug.

update_project

Rename a screen recording or file it under a project. Pass only what changes. Use it when the user says which project a recording belongs to, or wants a clearer title.

update_recording

Change fields on an existing task — rename it, move its status or priority, refile it under another project or milestone, set or clear the due date. Completing a task IS an update: pass status "done". Pass only what changes; null clears a nullable field.

update_task

Change the project or description of a logged time entry — for example file an entry that was tracked with no project. Take the entry id from list_time_entries. Pass only what changes.

update_time_entry