Skip to main content
Glama
Sign In

Montik

by app.montik
OverviewDiscussionsAdmin

List media

list_media
Read-only

Media library with bins, durations, resolution, loudness (LUFS; null = silent), AI tags and transcript status. from: folder lists the folder's media, uploaded once for every project in the folder; from: workspace lists the workspace's files the user can see, newest first; use_asset adds what you need here. from: deleted lists Recently deleted. They come a page at a time: pass next as cursor for more.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNofolder: the folder's media, shared by its projects; workspace: every file in the workspace's library, under the project or folder it lives in; deleted: Recently deleted, which restore_asset brings back (default: this project)
typeNo
cursorNonext, from the page before (from: folder or workspace come a page at a time)
projectIdNoProject to act on (default: the open one)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "next, from the page before (from: folder or workspace come a page at a time)",
+  "type": "string"
+}
    • changedInput schema / properties / from / description
      Previous value: -"folder: the folder's media, shared by its projects (default: this project)"New value: +"folder: the folder's media, shared by its projects; workspace: every file in the workspace's library, under the project or folder it lives in; deleted: Recently deleted, which restore_asset brings back (default: this project)"
    • changedInput schema / properties / from / enum
      Previous value: -[
-  "project",
-  "folder"
-]New value: +[
+  "project",
+  "folder",
+  "workspace",
+  "deleted"
+]
    • addedInput schema / properties / type
      Added value: +{
+  "enum": [
+    "video",
+    "audio",
+    "image"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "folder: the folder's media, shared by its projects (default: this project)",
+  "enum": [
+    "project",
+    "folder"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses useful behavioral details: returned media fields, `null = silent` for loudness, folder-level sharing semantics, workspace visibility and ordering, Recently deleted behavior, and cursor-based pagination. These details materially help an agent use the tool correctly.

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 dense but front-loaded and compact, using a few semicolon-separated clauses to cover return contents, scope routing, alternatives, and pagination. No sentence is wasted.

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?

For a read-only listing tool with no output schema, the description gives enough context about what is returned, how scopes differ, and how pagination works. An agent can call it correctly without needing additional explanation.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents most parameters at 75% coverage, but the description adds useful nuance about folder sharing, workspace visibility and ordering, deleted items, and passing `next` as the cursor. It does not add meaning for the `type` filter or `projectId`, leaving a small gap.

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: listing the media library, including bins, durations, resolution, loudness, AI tags and transcript status. It also distinguishes the available scopes (folder, workspace, deleted) so an agent can understand what this listing operation covers without opening the schema.

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 clearly explains when to use each `from` scope and routes agents to `use_asset` for adding assets. It does not explicitly mention alternatives such as `search_media` for filtered lookup, so the guidance is strong but not exhaustive.

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

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