`select_score`

Select score. Choose the music for an edit, with reasons.

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: "select_score", 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 draft's music.

Inputs

Input	Type	Needed	About
`editId`	string	yes	The edit id (its upload id) · format `^[a-f0-9]{24}$`
`assetId`	string	yes	format `^[a-z0-9][a-z0-9-]{0,159}$`
`version`	string	no	1 to 100 characters
`reasons`	array of string	no	up to 10 items
`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": "select_score",
  "arguments": {
    "editId": "editId",
    "assetId": "assetId"
  }
}

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.