content
See the content pipeline. See Marketing's content pipeline, read only: films, shorts and posts by stage.
Where it is
In the channel area (the content pipeline, results and the YouTube channel): open it with tools_for { area: "channel" }, then call it with read_tool { name: "content", args }.
Does it need a yes?
Reads only: it changes nothing. Here: the content pipeline.
Inputs
| Input | Type | Needed | About |
|---|---|---|---|
stage | string | no | Only this stage, e.g. script or scheduled. |
kind | "video" | "short" | "carousel" | "post" | no | Only this kind. |
run_id | string | no | The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters |
Example
{
"name": "content",
"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.