Oviond

List media files

list_media

Read-only

List media files

Input Schema

Name	Required	Description
`page`	No	Page number (0-indexed)
`limit`	No	Results per page, 1-100 (default 20)
`search`	No	Search term
`folder_id`	No	Filter by folder ID — read one off the folder a row reports in an unfiltered list. Media folders are created and managed in the app.

Output Schema

Name	Required	Description
`data`	No	One row per file — id, name, url, mime_type, size and the folder it sits in. The url is what you pass to branding, themes or an image widget.
`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 12, 2026
- 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: -"string"New value: +"integer"
```
- changedInput schema / properties / page / description
```
Previous value: -"Page number"New value: +"Page number (0-indexed)"
```
- addedInput schema / properties / page / minimum
```
Added value: +0
```
- changedInput schema / properties / page / type
```
Previous value: -"string"New value: +"integer"
```

Changed8 schema fields changedOct 5, 2026

removedInput schema / $schema

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

changedInput schema / properties / folder_id / description

Previous value: -"Filter by folder ID (from list_media / folders)"New value: +"Filter by folder ID — read one off the folder a row reports in an unfiltered list. Media folders are created and managed in the app."

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 file — id, name, url, mime_type, size and the folder it sits in. The url is what you pass to branding, themes or an image widget.",
+      "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

C2.2/5.0

Behavior2/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 fully covered by structured data. The description adds nothing beyond that — no pagination behavior, no default ordering, no note on what filtering combinations are supported. With annotations carrying the full burden, the description contributes no additional behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but this is under-specification rather than conciseness — the single phrase conveys no more than the tool name. Nothing is front-loaded because there is nothing substantive to load.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a list tool in a large sibling set with filtering and pagination parameters, the description leaves the agent unable to locate this tool against alternatives or understand the scope of results returned.

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 clearly documents page, limit, search, and folder_id, including the useful hint about reading folder IDs off an unfiltered list. Per the rubric, when coverage is high the baseline is 3 even with no parameter information in the description, which is the case here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

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?

There is no guidance on when to use this tool versus alternatives. The sibling set contains many other list_* tools and media-specific tools (archive_media_file, rename_media_file), yet the description gives no indication of when to pick list_media or what its role is in a workflow.

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?