Blend Create
blend_createCreate a blended datasource from 2–5 attached report tables by defining joins, join keys, dimensions, and metrics so charts can query combined output fields.
Instructions
Create a blend (Resource > Manage blends > Add a blend).
blend: {name, tables: [{datasource_id, dimensions: [field names], metrics: [{name, aggregation?}]}] (2-5 tables attached to the report, fields from datasource_get), joins: one per table after the first, in order: {join_type (LEFT_OUTER_JOIN default, INNER_JOIN, RIGHT_OUTER_JOIN, FULL_OUTER_JOIN, CROSS_JOIN, UNION), keys: [{left_table (earlier table index), left_field, right_field}]}} - key fields must be listed as dimensions. Output fields are built by the editor's own blend schema builder. Fingerprint from blends_list. Result blend_id is the datasource ID for components_create; output field names are what charts use. Input datasources need their schema loaded in the editor (SCHEMA_NOT_READY: use one in any chart first, or report_refresh). Table names, input filters and the date range dimension are set afterwards with blends_inputs_rename / blends_input_filters. One journalled report write, restorable with operation_restore.
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": {
"blend": "<blend>",
"expected_report_content_fingerprint": "<expected_report_content_fingerprint>"
},
"name": "blend_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| blend | Yes | ||
| dry_run | No | ||
| report_id | No | ||
| expected_report_content_fingerprint | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||