Skip to main content
Glama

Oviond

by com.oviond.api
OverviewDiscussionsAdmin

List archived items

list_archive
Read-only

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (0-indexed)
limitNoResults per page, 1-100 (default 20)
orderNoasc or desc
typesNoRestrict to these archive types (default: all)
searchNoFilter by name
sort_byNoSort field (default deleted_at)

Output Schema

NameRequiredDescriptionDefault
dataNoOne 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.
metaNoPage, limit and total row count.
successYesTrue when the call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Results per page"New value: +"Results per page, 1-100 (default 20)"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
  2. Changed7 schema fields changed
    • 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."
  3. Changed1 schema field changed
    • 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"
+}
  4. First observed

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's one added piece of context is that items are "soft-deleted," which is meaningfully more informative than a plain list. It adds nothing about pagination, retention, or mutability of these records.

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?

One front-loaded sentence with no filler, stating the resource and scope immediately. The inline enumeration of item types partially duplicates the schema's types enum rather than spending those words on usage guidance.

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?

An output schema exists and the input schema is fully described, so return values need not be explained. For a read-only paginated list tool the description is nearly sufficient; only the relationship to restore_from_archive 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% and all six parameters (page, limit, order, types, search, sort_by) are documented with defaults and enums. The description adds no syntax, defaults, or behavioral notes beyond the schema, so the baseline 3 applies.

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?

Clear verb+resource ("List soft-deleted (archived) items") and it disambiguates the archive concept from the many list_* siblings by stating these are soft-deleted records. It does not name the complementary sibling restore_from_archive, but the purpose is unambiguous without it.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance. The natural workflow partner restore_from_archive is never mentioned, and there is no indication of when to prefer this over the per-type list_* tools or how the default of all types behaves.

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

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