Meta Council

Update Saved View

update_saved_view

Revise one of YOUR OWN saved views in place, keeping its id and any existing team share. Only the fields you send change; the rest are left exactly as they were, while scorecard-enrolled views require the current definition_revision; after a conflict or uncertain reply, read current state and deliberately reconcile. Sharing a view does not let its readers revise it -- only the owner may. Requires authentication and the tickets:write scope.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New name for the view.
`columns`	No	Replacement column list, 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	New sorting field; null clears it. Clear explicit grouping and sorting when switching to triage.
`view_id`	Yes	The view's id, from list_saved_views.
`group_by`	No	New grouping field; null clears it. Clear explicit grouping and sorting when switching to triage.
`sort_dir`	No	New sort direction.
`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"
+]

Changed9 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"
+  ]
+}

changedInput schema / properties / group_by / description

Previous value: -"New grouping field."New value: +"New grouping field; null clears it. Clear explicit grouping and sorting when switching to triage."

changedInput schema / properties / group_by / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / sort_by / description

Previous value: -"New sort field."New value: +"New sorting field; null clears it. Clear explicit grouping and sorting when switching to triage."

changedInput schema / properties / sort_by / type

Previous value: -"string"New value: +[
+  "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

A4.6/5.0

Behavior5/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent mutation, and the description goes well beyond that: partial-update semantics ('only the fields you send change; the rest are left exactly as they were'), a concurrency contract (scorecard-enrolled views require the current definition_revision), conflict-handling guidance ('read current state and deliberately reconcile'), and authorization/scope requirements.

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 the core in-place revise action, and every clause (ownership, partial update, revision guard, reconciliation, scope) carries distinct operational value. It is dense with semicolon-joined clauses that could be split for readability, but there is no filler.

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 9-param mutation tool with nested objects and no output schema, the description covers the essentials an agent needs: ownership constraint, auth/scope, partial-update behavior, concurrency/revision handling, and conflict reconciliation. Nothing critical to invoking it correctly 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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: it clarifies expected_revision as the concurrency token required to configure a scorecard or touch an enrolled view, and explains that unspecified fields are preserved. This links the key parameter to behavior beyond 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 (revise) and resource (saved view) and scopes it precisely to 'one of YOUR OWN' views, updated 'in place, keeping its id and any existing team share' – this cleanly separates it from create_saved_view, archive_saved_view, restore_saved_view, and delete_saved_view.

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?

Gives clear invocation context: only the owner may revise, and sharing a view does not grant readers revision rights, plus the required auth and tickets:write scope. It stops short of explicitly naming sibling alternatives (e.g. use create_saved_view to make a new one), so it reaches clear context but not explicit when-not/alternative routing.

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?