Skip to main content
Glama

Create, edit or delete one of the user's custom views (applies immediately)

manage_view
Destructive

Saves 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

NameRequiredDescriptionDefault
nameNocreate (required) and update: the view's name, 1 to 60 characters.
specNoA 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.
actionYescreate a view, update one (by viewId), or delete one (by viewId).
viewIdNoupdate and delete only: the `id` of a saved view, exactly as get_views returns it.

Output Schema

NameRequiredDescriptionDefault
viewNoThe view acted on (with its spec after a create or update).
errorNoPresent 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.
statusNoWhat happened, and it already happened: created / updated / deleted for manage_view; added / already / full for add_view_to_dashboard (already and full changed nothing).
messageNoPlain-language explanation that accompanies `error`, `data_status` or a proposed change. Read it to the user.
profileNoThe portfolio these figures belong to (absent on list_profiles).
previousNoAfter an update: what it was.
view_urlNo
next_stepNoWhat the user should do about data_status.
source_urlNoLink to the page in the WhereItGoes app that shows this data.
data_statusNoPresent 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_urlNoWhere the user can upgrade, on an upgrade_required refusal.
stock_assetsNoPresent when the answer mentions Binance Stocks shares (EQ_<ticker>): they are US stocks, not crypto.
removed_from_dashboardsNoAfter a delete: how many dashboards it was taken off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantial context beyond them: changes apply immediately with no approval link (unlike the settings tools), the user can undo from the Views page, and delete also removes the view from every dashboard it was on. It also discloses that update replaces only the fields sent and that unexpected arguments are refused. The one gap is that it never says what the call returns, though an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The per-action breakdown is front-loaded and each sentence carries operational information the agent needs to avoid a wrong call. It is dense rather than padded, though the 1-to-60-character name limit and the spec shape are repeated from the schema, which is mild redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive multi-action mutation, the description covers immediacy of effect, undo path, cross-tool dependencies (get_views, preview_view, add_view_to_dashboard), permission failure mode, and argument validation. Return values are covered by the existing output schema, so nothing an agent needs to call this safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description genuinely adds meaning on top: it maps which parameters each action requires (create needs name and spec; update needs viewId plus name, spec or both; delete takes viewId only) and clarifies that update semantics are replacement, not merge. It also ties spec validation to preview_view and spec sourcing to get_views, which the schema does not express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific verb family (saves changes) and resource (the user's custom views) and immediately explains that behavior branches on `action`. The create/update/delete breakdown lets an agent separate this from get_views, preview_view, list_view_sources and add_view_to_dashboard without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing is given for every action: fetch the current spec from get_views before updating, call add_view_to_dashboard after creating, and confirm with the user before deleting a view they did not ask to remove. It also states the prerequisite permission and the required response when it is missing (write_not_permitted, read it out and stop).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.