run_pipeline
Chain ops in one call: each step is {op, input?, args?, as?, input_type?}, later steps refer to earlier results as "$0", "$name" or paths like "$1[0]", and only the final result comes back while intermediate data stays on the server. Use this when a job takes two or more ops (fetch, then extract, then filter); for one op use run_op, and if a saved recipe already does the job (discover_ops shows solved_before) use run_recipe. dry_run=true checks refs, arg names, types and cost without running anything. Up to 50 steps. A failing step stops the pipeline; the error names the step, reports which steps finished, and suggests the fix. Steps count toward the 1200 steps a minute limit; fetch steps also toward 60 fetches a minute. Example steps: [{"op": "fetch", "args": {"url": "https://example.com/pricing"}, "as": "page"}, {"op": "extract_tables", "input": "$page", "args": {"index": 0}}, {"op": "to_markdown", "input": "$1"}].
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"steps": "<steps>"
},
"name": "run_pipeline"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| steps | Yes | Ordered steps, 1 to 50. A literal string starting with $ is written $$. | |
| terse | No | Return only the answer (value, or handle and preview), without steps, hashes or hints. | |
| dry_run | No | Validate and estimate without running. | |
| result_from | No | Which step to return, as a ref like "$2" or "$prices[0]". Default: the last step. | |
| inline_max_tokens | No | Return the value itself when it's at most this many estimated tokens, else a preview. Default 300. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| steps | No | Per step: op, handle, type, est_tokens, ms. | |
| valid | No | dry_run: whether it would run. | |
| value | No | terse: the value itself. | |
| handle | No | terse, large result: its handle id. | |
| result | No | The returned step's handle, as in run_op. | |
| totals | No | dry_run: the estimate: steps, cost, side effects (e.g. reads_network), deterministic. | |
| problems | No | dry_run: what would fail, per step. |