Meta Council

Delete Saved View

delete_saved_view

Destructive

Permanently delete one of YOUR OWN saved views. UNRECOVERABLE -- there is no undo and the definition is not retained. archive_saved_view is the reversible retirement and is almost always what is wanted instead; use this only for a view that should actually be gone. Deleting a shared view removes it for the team too. Requires authentication and the tickets:write scope.

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": {
      "view_id": "<view_id>"
    },
    "name": "delete_saved_view"
  }
}

Input Schema

Name	Required	Description	Default
`view_id`	Yes	The view's id, from list_saved_views.
`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.

Changed1 schema field 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"
+}

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.7/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes well beyond them: unrecoverable with no undo, the definition is not retained, and deleting a shared view removes it for the team. It also discloses the authentication and tickets:write scope requirement, which annotations do not cover.

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?

Four tight sentences, front-loaded with the irreversibility warning and then the alternative routing. Every sentence carries distinct information: consequence, alternative, blast radius, auth requirement.

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, no-output mutation tool, the description covers the safety profile, the alternative, the sharing side effect, and the auth/scope needs. Nothing an agent needs to call this correctly is missing.

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 view_id (sourced from list_saved_views) and expected_revision are already documented in the schema. The description adds no further meaning about parameter format or the revision-conflict reconciliation semantics, so the baseline 3 applies.

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 (permanently delete) and resource (saved views), plus an ownership constraint (YOUR OWN). It explicitly names the closest sibling, archive_saved_view, and contrasts reversible vs. permanent, so an agent can distinguish it without reading either 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?

Gives explicit when-not guidance ('archive_saved_view is the reversible retirement and is almost always what is wanted instead; use this only for a view that should actually be gone'), naming both the alternative and the condition that selects it. Nothing is left to inference.

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?