Oviond

Archive multiple media files

archive_media_files

Destructive

Archive several media files by ID in one call. They go to the archive, not away — list_archive shows them and restore_from_archive brings them back.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	Yes	Media file IDs to archive (from list_media)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	Confirmation of the archive, and how many files it covered.
`success`	Yes	True when the call succeeded. A failure comes back as an error result instead.

Schema Changelog

Changes observed during successful MCP inspections.

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": "Confirmation of the archive, and how many files it covered."
+    },
+    "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

A4.3/5.0

Behavior4/5

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

The description adds valuable behavioral context beyond the destructiveHint and readOnlyHint annotations: it clarifies that archiving is not permanent ('not away') and that archived media can be listed and restored. It does not cover partial failures or metadata retention, but for a reversible archive operation this is sufficient.

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?

The description is two sentences with no wasted words. The first sentence states the action and scope; the second sentence disambiguates the permanence of the operation and names the recovery tools.

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?

Given the single well-documented parameter, the output schema, and the annotations, the description is complete. It explains what happens to the files, where they appear, and how to reverse the operation, so an agent has enough context to call this tool correctly.

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 the schema already documents ids as 'Media file IDs to archive (from list_media)' with minItems: 1. The description adds only that the operation is batched by ID, which matches the schema without providing additional parameter-level meaning.

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?

The description states a specific verb and resource: 'Archive several media files by ID in one call.' It clearly distinguishes this batch tool from the singular sibling archive_media_file and from other archive_* tools that target different resource types.

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?

The description establishes the main use case — archiving multiple files in a single batch call — and explains the recovery path via list_archive and restore_from_archive. It does not explicitly name an alternative for permanent deletion, but the context is clear enough given the tool's reversible behavior.

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?