What it does
Open a run — one work session on a task — when you begin substantive work. Returns the run id (pass it to end_run) and the task's budget (budget_tool_calls / budget_minutes, null = uncapped) with cumulative usage so far, so you can pace yourself. Enforced: if the task has already spent its whole budget across earlier runs, start_run is refused (error budget_exceeded) — a human must raise the budget or take over. Every run leaves an auditable trace in the task's activity.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | string | Required | Task id |
trace_url | string | Optional | Absolute http(s) link to this run's session transcript, if you have one (any other scheme is refused). Turns the run record into something a human can open when they ask why you did what you did — especially for work that happened overnight. |
agent | string | Optional | Your agent id, recorded on the run so per-agent history is reconstructable. Ignored if your token has a name of its own — a named credential is the identity, and this argument is only the fallback for an unnamed one. |
Annotations
The hints the server sends with this tool. A host reads them to decide whether to ask you before a call.
- Read-only
readOnlyHint: false - Changes data in your Done account.
- Destructive
destructiveHint: false - Only adds or reads; nothing already there is removed or overwritten.
- Idempotent
idempotentHint: false - Each call can add something new, such as a comment, a run or a task.
- Open world
openWorldHint: false - Touches only your own Done account.
Which tokens can call it
A connection made with OAuth has full access. A token from Settings → Agent access → Extra MCP tokens can be narrowed, and a narrowed token never sees beyond its project or workspace.
- Full accessAllowed
- Read-only tokenRefused
- Single-project tokenRefused
- Single-workspace tokenAllowed
Try it
With Done connected, ask your assistant something like:
“Log a run while you work on this task, so I can see what it cost.”
Connect Done to your assistant
One MCP endpoint per account, over OAuth or a token. Step-by-step setup for each client: