Oviond

List archived items

list_archive

Read-only

List soft-deleted (archived) items across clients, reports, media, automations and templates.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (0-indexed)
`limit`	No	Results per page
`order`	No	asc or desc
`types`	No	Restrict to these archive types (default: all)
`search`	No	Filter by name
`sort_by`	No	Sort field (default deleted_at)

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	One row per archived item — id, name, its archive type (clients, projects, media, automations, templates) and deleted_at. Pass the id and type to restore_from_archive.
`meta`	No	Page, limit and total row count.
`success`	Yes	True when the call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 5, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedOutput schema / properties / meta / description

Previous value: -"Pagination for the list — page, limit and the total row count."New value: +"Page, limit and total row count."

changedOutput schema / properties / meta / properties / limit / description

Previous value: -"Maximum rows per page."New value: +"Max rows per page."

changedOutput schema / properties / meta / properties / page / description

Previous value: -"Zero-based index of the page returned."New value: +"Page index, zero-based."

changedOutput schema / properties / meta / properties / total / description

Previous value: -"Total rows matching the query across all pages."New value: +"Total rows matching the query."

changedOutput schema / properties / success / description

Previous value: -"True when the call succeeded. A failure comes back as an error result instead."New value: +"True when the call succeeded."

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "One row per archived item — id, name, its archive type (clients, projects, media, automations, templates) and deleted_at. Pass the id and type to restore_from_archive.",
+      "items": {},
+      "type": "array"
+    },
+    "meta": {
+      "additionalProperties": true,
+      "description": "Pagination for the list — page, limit and the total row count.",
+      "properties": {
+        "limit": {
+          "description": "Maximum rows per page.",
+          "type": "number"
+        },
+        "page": {
+          "description": "Zero-based index of the page returned.",
+          "type": "number"
+        },
+        "total": {
+          "description": "Total rows matching the query across all pages.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the call succeeded. A failure comes back as an error result instead.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedSep 18, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral context that the items are soft-deleted rather than permanently removed, but it does not disclose other behavior such as whether all types are included by default or how filters interact.

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 a single sentence with no filler and front-loads the core action and scope. The main issue is that the type list is inaccurate, but structurally it is concise and readable.

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

Completeness3/5

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

The output schema and annotations carry much of the burden, so the description does not need to explain return values or safety. It is incomplete because it under-lists the available archive types and includes an invalid one, so the agent could form a wrong mental model of the tool's scope despite having the schema.

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

Parameters2/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 actively misleads by enumerating types that partially conflict with the schema: it mentions 'reports' which is not in the types enum, and omits many valid types like projects, goals, assets, and custom_data. Rather than adding meaning, the description introduces incorrect parameter semantics.

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?

The description names a specific verb and resource: it lists soft-deleted/archived items, which distinguishes it from the active list_* sibling tools. However, the type list it gives ('clients, reports, media, automations and templates') is inconsistent with the schema, which has no 'reports' type and includes many additional types, creating some ambiguity.

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?

The phrase 'soft-deleted (archived)' implies this tool is for retrieving archived items rather than active ones, giving some usage context relative to sibling list tools. It does not explicitly say when not to use it or mention alternatives such as restore_from_archive, so guidance is implied rather than explicit.

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

All Oviond 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?