Save Todo
save-todoAdd, update, complete, reopen or delete an item on the team's to-do list for this property. Add a to-do whenever the user asks, and also on your own initiative for concrete follow-ups the conversation turns up (a fix to make, something to re-check on a later date, a test to run) — it is better to note a follow-up than to let it be forgotten. Every time you add, complete or reopen a to-do, say so plainly in your reply (e.g. "Added to the to-do list: ..."), because users do not always read the whole answer. Complete a to-do only when the user says it is done or the data in this conversation clearly shows it; never delete one unless the user asks. Before adding, call list_todos and prefer updating an existing item over creating a duplicate. Write titles as short imperative actions; put context and the reason in notes.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | Optional context: why it matters, what was found, where to look | |
| title | No | Short imperative action, max 200 characters (required for add) | |
| action | Yes | add = new to-do, update = edit fields of an existing one, complete = tick off, reopen = un-tick, delete = remove | |
| todo_id | No | The to-do id from list_todos, e.g. "t:1a2b3c4d" (required for every action except add) | |
| due_date | No | Optional due date as YYYY-MM-DD (e.g. when to re-check a metric). Send an empty string on update to clear it. | |
| property | Yes | ID of the AIdata property this call targets. Call the list_properties tool to see the properties you can access. | |
| important | No | Mark as important (starred) |