Skip to main content
Glama

List saved views

well_list_views
Read-only

List the saved views of one records root: the tabs of the records table in the Well web app, each with its own filters, sort, columns and layout. Use it when the person names a view ("my overdue invoices view") to get its view_id, then pass it as viewId to well_show_records or well_query_records.

Each view carries view_id, name, root, layout_type (one of table, kanban, calendar, gallery, chart, list, graph, timeline, or null) and is_default (the root's default tab). At most 50 views come back, the default first, then the newest; total is how many the root holds.

success: false means the views could not be read, NOT that the root has none.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
rootYesThe records root whose saved views to list, for example invoices or companies.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
errorNo
totalNo
viewsYes
successYes
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / views / items / properties / layout_type / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "table",
      -      "kanban",
      -      "calendar",
      -      "gallery",
      -      "chart",
      -      "list",
      -      "graph"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "table",
      +      "kanban",
      +      "calendar",
      +      "gallery",
      +      "chart",
      +      "list",
      +      "graph",
      +      "timeline"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the readOnlyHint/non-destructive annotations: documents the 50-view cap and ordering (default first, then newest), the `total` field, the exact per-view fields returned, and the non-obvious failure mode that `success: false` means unreadable views rather than an empty root. Also discloses the multi-workspace behavior (no guessing).

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?

Front-loaded with purpose and the key routing instruction, with a bolded failure-mode warning. The workspace guidance is repeated (in the body and again in the closing paragraph) and overlaps the schema's own workspace_id description, which is the only real waste.

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?

Complete for a read-only list tool with an output schema: response fields, cap, ordering, total, failure semantics and the view_id handoff are all covered. An agent can call it and act on the result without consulting anything else.

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, but the description adds real meaning: it shows what `root` looks like (invoices, companies), explains that the returned `view_id` feeds `viewId` elsewhere, and states the concrete workspace_id condition. `conversation_id` and `workspace_scope` still rely entirely on the schema text.

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?

States a specific verb and resource ('List the saved views of one records root') plus a concrete gloss ('the tabs of the records table in the Well web app, each with its own filters, sort, columns and layout'). That gloss distinguishes it from well_show_records, well_query_records and well_create_workspace_view, which are the nearest siblings.

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?

Gives an explicit trigger ('Use it when the person names a view ...') and the follow-on step ('pass it as viewId to well_show_records or well_query_records'), naming the sibling tools. It also resolves the workspace ambiguity with a when-to-pass-the-workspace_id rule and states that no prior workspace call is needed.

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.

Resources