Start a running timer
keeping_start_timerDestructive
Start a new running timer. Use dry-run to preview the entry, then confirm with human approval to log it.
Instructions
Start a new ongoing time entry (a running timer). Implemented as POST /{orgId}/time-entries with start set and NO end / NO hours — Keeping interprets the omission of end as 'this entry is ongoing'. Returns { timer_id } on success; use this id with keeping_stop_timer or keeping_resume_timer. DRY-RUN BY DEFAULT — call without confirm first to receive a would_post preview; call again with confirm: true ONLY after a human reviewed the preview. start defaults to the current time in Europe/Amsterdam; purpose defaults to 'work'.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| start | No | HH:mm in org timezone; defaults to the current time in Europe/Amsterdam when omitted. | |
| confirm | No | Set to true ONLY after a human has reviewed the would_post preview returned by a prior dry-run call. The MCP client (LLM) MUST NOT set this autonomously — wait for the human to type 'yes' / 'confirm'. | |
| purpose | No | Time-entry category. Maps to Keeping's purpose enum; billable status is determined at the project level. | work |
| task_id | No | ||
| project_id | No | ||
| organisation_id | No | Override KEEPING_ORG_ID; required for multi-org tokens. |