Place a saved custom view on the user's dashboard (applies immediately)
add_view_to_dashboardAdds one of the user's saved views to the dashboard of a portfolio, at the end, as a widget. Applies immediately, and is safe to repeat: a view already there answers already and nothing changes. A dashboard holds at most 24 widgets; a full one answers full and nothing is added, so tell the user to remove one in the app. size is "full" (default, the whole row) or "half". Each portfolio has its own dashboard, picked by profile. Needs the connection's "make changes" permission (write_not_permitted otherwise).
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": {
"viewId": "<viewId>"
},
"name": "add_view_to_dashboard"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | "full" (default) spans the row; "half" sits beside another half-width widget. | |
| viewId | Yes | The view to place: the `id` of a saved view, exactly as get_views returns it. | |
| profile | No | Which portfolio to read, for accounts with more than one: its id, or its name (exact, case-insensitive, e.g. "Trading"). Omit to read this connection's default portfolio; every answer names the portfolio it read in `profile`. An unknown or shared name returns profile_not_found or profile_ambiguous listing the real ones, and list_profiles shows them up front. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| view | No | The view acted on (with its spec after a create or update). | |
| error | No | Present ONLY when the call was refused instead of answered: upgrade_required (Pro plan needed), not_found, profile_not_found, profile_ambiguous, invalid_arguments, write_not_permitted, rate_limited, limit_reached, view_unavailable. No data fields come with it; read `message` to the user rather than retrying the same call. | |
| status | No | What happened, and it already happened: created / updated / deleted for manage_view; added / already / full for add_view_to_dashboard (already and full changed nothing). | |
| message | No | Plain-language explanation that accompanies `error`, `data_status` or a proposed change. Read it to the user. | |
| profile | No | The portfolio these figures belong to (absent on list_profiles). | |
| previous | No | After an update: what it was. | |
| view_url | No | ||
| next_step | No | What the user should do about data_status. | |
| source_url | No | Link to the page in the WhereItGoes app that shows this data. | |
| data_status | No | Present only when the portfolio has no data yet. nothing_connected: no exchange and no wallet is connected, so empty lists and zeros mean "no data", NOT a $0 portfolio, and no data fields come with it (except on get_connections, get_alerts, get_target_allocation and list_profiles, which also answer). Send the user to next_step. syncing: a source is connected but its first sync is still running, so figures are partial and not final. | |
| upgrade_url | No | Where the user can upgrade, on an upgrade_required refusal. | |
| stock_assets | No | Present when the answer mentions Binance Stocks shares (EQ_<ticker>): they are US stocks, not crypto. | |
| removed_from_dashboards | No | After a delete: how many dashboards it was taken off. |