get_assets
Get assets. Read up to 100 pieces at once.
Where it is
In the media area (films, carousels and pictures in the media library): open it with tools_for { area: "media" }, then call it with read_tool { name: "get_assets", args }.
Does it need a yes?
Reads only: it changes nothing. Here: read.
Inputs
| Input | Type | Needed | About |
|---|---|---|---|
assetIds | array of string | yes | 1 to 100 items |
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": "get_assets",
"arguments": {
"assetIds": [
"assetIds"
]
}
}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.