Create, edit or delete one of the user's custom views (applies immediately)
manage_viewSaves changes to the user's custom views, picked by action. create: name (1 to 60 characters) and spec. update: viewId plus name, spec or both; what you send replaces that part, and edits apply to any of the user's views, including ones they made by hand. delete: viewId only; the view also leaves every dashboard it was on. Unlike the settings tools, this APPLIES IMMEDIATELY, with no approval link: tell the user it is done, and that they can undo a mistake from the Views page. Create and update are not destructive; delete is, so confirm with the user before deleting a view they did not ask you to remove. A new view is NOT on the dashboard until you call add_view_to_dashboard. Specs are validated like preview_view; get the current spec from get_views before an update. Needs the connection's "make changes" permission (write_not_permitted otherwise; read it out and stop). An argument the action does not take is refused.
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": {
"action": "<action>"
},
"name": "manage_view"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | create (required) and update: the view's name, 1 to 60 characters. | |
| spec | No | A view spec: the JSON object list_view_sources describes ({"v":1,"source":...,"columns":[...],"render":{...}}). Only catalog keys, no expressions or SQL. A JSON string of the same object is accepted too. | |
| action | Yes | create a view, update one (by viewId), or delete one (by viewId). | |
| viewId | No | update and delete only: the `id` of a saved view, exactly as get_views returns it. |
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. |