list_edits
List edits. Edits (uploads), newest first. mine: only those you sent or picked up.
Where it is
In the edits area (edits, looks, formats, music, scores and the owner's notes on media): open it with tools_for { area: "edits" }, then call it with read_tool { name: "list_edits", args }.
Does it need a yes?
Reads only: it changes nothing. Here: list.
Inputs
| Input | Type | Needed | About |
|---|---|---|---|
status | "uploading" | "received" | "claimed" | "working" | "ready" | "failed" | no | |
mine | boolean | no | |
awaitingOwner | boolean | no | |
limit | integer | no | 1 to 200 |
run_id | string | no | Your run id from the connector's start, so the output ties back to this session · format `^[A-Za-z0-9_.:@-]{1,120}$` |
Example
{
"name": "list_edits",
"arguments": {}
}When it is refused
invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.taken: Someone else holds it (another AI on that task). Pick another task.stale: It changed since you read it. Read it again and use the new version.failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.