Skip to main content
Glama

oviond

by com.oviond
OverviewDiscussionsAdmin

List media files

list_media
Read-only

List media files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
limitNoResults per page
searchNoSearch term
folder_idNoFilter 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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • 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."
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no additional behavioral context: it does not mention pagination behavior, default limits, ordering, or whether archived media files are included. It essentially restates the title without contributing new transparency.

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

Conciseness3/5

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

The description is a single short sentence with no wasted words, but it is under-specified for a tool with four optional filtering parameters and pagination. It is concise in length but not optimally sized because it omits useful context about filtering and pagination that would help an agent invoke it correctly.

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 read-only annotations cover return shape and safety, and the input schema documents all parameters. What is missing is usage guidance and any behavioral detail beyond the bare function; for a listing tool, this is minimally adequate but not complete.

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%, with page, limit, search, and folder_id each having a description in the input schema. The tool description itself adds no extra parameter meaning, so it does not elevate above the baseline established by the schema. The folder_id description in the schema is actually more informative than anything in the tool description.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer from the name that this is the tool for listing media files; there is no mention of when list_assets, search, or archive_media_file would be more appropriate.

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