results
See the results. See what came of the work, read only: sign-ups by source, and posted pieces with their numbers. At most 366 days at once, from before to.
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: "results", args }.
Does it need a yes?
Reads only: it changes nothing. Here: the company's numbers.
Inputs
| Input | Type | Needed | About |
|---|---|---|---|
since | string | no | The first day, e.g. 2026-10-19 (company time). 29 days before until if left out. |
until | string | no | The last day, included (today if left out). |
by | "source" | "post" | "channel" | "page" | "campaign" | no | source (the default), post, channel, page or campaign (the utm_source of the link they came through). |
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": "results",
"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.