Meta Council

Create Saved View

create_saved_view

Save a named ticket filter, column, grouping and sort bundle so you can reopen it later or share it with a team. Saves the QUESTION, not an answer: the view is re-run against live tickets every time it is opened, so it never goes stale. The new view is private until you share it. Same endpoint the web app's save button uses. Requires authentication and the tickets:write scope.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	What to call the view.
`columns`	Yes	Which ticket columns the view shows, in order. At most 20.
`filters`	No	Saved question. Omitted reader selects ordinary tickets. Attention accepts reason; reviewed_attention accepts state and follow_up. Triage refuses other non-default ticket filters, grouping and sorting. Save intent only, never result pages.
`sort_by`	No	Optional ticket field to sort rows by.
`group_by`	No	Optional ticket field to group rows by.
`sort_dir`	No	Sort direction. Defaults to asc.	asc
`scorecard`	No	Optional private ordinary live ticket counts; omit to retain, null to clear while retaining a nonzero revision. At most 10000 matching tickets, no actions or role grants. Shared and triage definitions cannot enroll.
`expected_revision`	No	Current definition_revision, required to configure a scorecard or change any previously enrolled view. On conflict or uncertain reply, read current state and deliberately reconcile; this is not an exact-retry receipt.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / expected_revision

Added value: +{
+  "description": "Current definition_revision, required to configure a scorecard or change any previously enrolled view. On conflict or uncertain reply, read current state and deliberately reconcile; this is not an exact-retry receipt.",
+  "maximum": 2147483647,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / scorecard

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional private ordinary live ticket counts; omit to retain, null to clear while retaining a nonzero revision. At most 10000 matching tickets, no actions or role grants. Shared and triage definitions cannot enroll.",
+  "properties": {
+    "cards": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "metric": {
+            "enum": [
+              "total",
+              "open",
+              "todo",
+              "in_progress",
+              "blocked",
+              "done",
+              "cancelled"
+            ],
+            "type": "string"
+          },
+          "threshold": {
+            "additionalProperties": false,
+            "properties": {
+              "operator": {
+                "enum": [
+                  "gte",
+                  "lte"
+                ],
+                "type": "string"
+              },
+              "value": {
+                "maximum": 2147483647,
+                "minimum": 0,
+                "type": "integer"
+              }
+            },
+            "required": [
+              "operator",
+              "value"
+            ],
+            "type": [
+              "object",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "metric",
+          "threshold"
+        ],
+        "type": "object"
+      },
+      "maxItems": 7,
+      "minItems": 1,
+      "type": "array"
+    },
+    "preset": {
+      "enum": [
+        "custom",
+        "executive",
+        "pmo",
+        "manager"
+      ],
+      "type": "string"
+    },
+    "version": {
+      "const": 1,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "version",
+    "preset",
+    "cards"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / filters / properties / reason / enum

Previous value: -[
-  null,
-  "stale",
-  "aging",
-  "blocked",
-  "dependency_blocked",
-  "completion_blocked",
-  "missed_due_date",
-  "integration_drift"
-]New value: +[
+  null,
+  "stale",
+  "aging",
+  "blocked",
+  "dependency_blocked",
+  "completion_blocked",
+  "missed_due_date",
+  "integration_drift",
+  "forecast_degradation"
+]

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / filters / properties / reason / enum

Previous value: -[
-  null,
-  "stale",
-  "aging",
-  "blocked",
-  "dependency_blocked",
-  "completion_blocked",
-  "missed_due_date"
-]New value: +[
+  null,
+  "stale",
+  "aging",
+  "blocked",
+  "dependency_blocked",
+  "completion_blocked",
+  "missed_due_date",
+  "integration_drift"
+]

Changed5 schema fields changedSep 27, 2026

changedInput schema / properties / filters / description

Previous value: -"Which tickets the view selects. Same filter vocabulary the ticket list accepts; omitted filters are unset."New value: +"Saved question. Omitted reader selects ordinary tickets. Attention accepts reason; reviewed_attention accepts state and follow_up. Triage refuses other non-default ticket filters, grouping and sorting. Save intent only, never result pages."

addedInput schema / properties / filters / properties / follow_up

Added value: +{
+  "description": "Saved-view filter: follow_up.",
+  "enum": [
+    null,
+    "all",
+    "due"
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / filters / properties / reader

Added value: +{
+  "default": "tickets",
+  "description": "Saved-view filter: reader.",
+  "enum": [
+    "tickets",
+    "attention",
+    "reviewed_attention"
+  ],
+  "type": "string"
+}

addedInput schema / properties / filters / properties / reason

Added value: +{
+  "description": "Saved-view filter: reason.",
+  "enum": [
+    null,
+    "stale",
+    "aging",
+    "blocked",
+    "dependency_blocked",
+    "completion_blocked",
+    "missed_due_date"
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / filters / properties / state

Added value: +{
+  "description": "Saved-view filter: state.",
+  "enum": [
+    null,
+    "unresolved",
+    "resolved",
+    "all"
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedSep 21, 2026

addedInput schema / properties / filters / properties / scope

Added value: +{
+  "default": "active",
+  "description": "Saved-view filter: scope.",
+  "enum": [
+    "active",
+    "archived",
+    "all"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null

AddedAug 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive mutation. The description adds real behavioral context beyond that: it requires authentication and the tickets:write scope, the view is private until shared, and it stores the query rather than results so it re-runs live. It omits any note on failure/revision conflict, though that lives in the schema's expected_revision field.

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

Conciseness5/5

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

Front-loads the core purpose, then adds three short, distinct and useful clarifications (query-not-results, private-by-default, auth/scope). Every sentence carries a distinct fact with no redundancy.

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

Completeness4/5

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

For a complex 8-parameter tool with nested objects and no output schema, the description covers auth, privacy, and the live re-run semantics well. It does not address the revision/conflict workflow, but that requirement is documented on expected_revision in the schema, so the gap is minor.

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

Parameters3/5

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

Schema description coverage is 100%, so the parameters are largely self-documenting and the baseline is 3. The description adds conceptual framing ('saves the QUESTION, not an answer') that clarifies the intent of the filters object, but gives no field-level meaning beyond what the schema already carries.

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

Purpose4/5

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

States a specific verb (Save) and resource (a named ticket filter/column/grouping/sort bundle), which is far more precise than the bare name. It doesn't name the neighboring operations (update_saved_view, execute_saved_view, share_saved_view) explicitly, though 'reopen it later or share it with a team' implies the create-vs-use-vs-share boundary.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the reader infers you call this to persist a new view, but there is no explicit when-to-use versus update_saved_view (modify an existing view) or execute_saved_view (run it). No exclusions or preconditions for choosing this tool over its siblings are given.

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

All Meta Council tools Inspect

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

Need Help?