Skip to main content
Glama

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

List Saved Views

list_saved_views
Read-onlyIdempotent

List saved ticket views you can open: the stored filter, column, grouping and sort combinations saved by you, plus any shared with a team you belong to. Shared views appear under the active and all scopes and never once archived, because an owner's archive is their own working state. Returns the same payload the web app's saved-view list returns. Requires authentication and the tickets:read scope. Pages use immutable creation-time/ID order; follow next_cursor while has_more. Current permissions and archive state are rechecked on every page; this is live metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many views per page. Defaults to 50.
scopeNoWhich of YOUR OWN views to include: active (the default, excluding archived), archived (your recovery list), or all. Shared views are unaffected by archived and never appear under it.
cursorNoOpaque next_cursor from the same caller and scope; expires after 24 hours. Omit to refresh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque next_cursor from the same caller and scope; expires after 24 hours. Omit to refresh.",
+  "maxLength": 1024,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"How many views to return. Defaults to 50."New value: +"How many views per page. Defaults to 50."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate read-only and idempotent hints, but the description adds important behavioral details: shared views are never archived because an owner's archive is their own working state, pagination uses immutable creation-time/ID order, and permissions/archive state are rechecked on every page. This is beyond the annotations.

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 description is concise, front-loads the core purpose, and adds critical nuances without being verbose. It could be slightly tighter, but each sentence provides useful information.

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?

Given the tool's moderate complexity, the description covers purpose, authentication, pagination, and edge cases (shared views, archive behavior). It provides sufficient context without an output schema, and the live metadata behavior is clearly explained.

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 parameters are well-documented. The description adds value by explaining the scope parameter's effect on shared views and the cursor's expiration, but these are minor additions over the schema.

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 description states a specific verb ('List') and resource ('saved ticket views'), and clarifies that it includes both personal and team-shared views. It distinguishes from siblings like get_saved_view and execute_saved_view by focusing on listing rather than retrieving or executing.

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

Usage Guidelines4/5

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

The description mentions authentication and scope requirements ('Requires authentication and the tickets:read scope'), and the scope parameter distinguishes between active, archived, and all views. It doesn't explicitly name alternatives like get_saved_view, but the context makes it clear when list_saved_views is appropriate.

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

All Meta Council toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources