`add_edit_note`

Add edit note. Add a note to an edit that the next revision reads (the owner sees it too).

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 use_tool { name: "add_edit_note", args }.

Does it need a yes?

Runs at once, no yes card: it changes only the office's own working state, and nothing reaches anyone. Here: a note.

Inputs

Input	Type	Needed	About
`id`	string	yes	The edit id (its upload id) · format `^[a-f0-9]{24}$`
`text`	string	yes	1 to 2,000 characters
`requestId`	string	no	format `^[A-Za-z0-9_.:@-]{6,100}$`
`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": "add_edit_note",
  "arguments": {
    "id": "id",
    "text": "Hi Ana, thanks for your message."
  }
}

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.