cuttingfloor

List media

media.list

Read-onlyIdempotent

What the user has here: imported and created media, and files they sent that aren't imported yet (through media.upload's link, or dropped on the cuttingfloor site), with names, sizes and when each expires, plus this account's storage used and how much it holds. When the user mentions a file they sent or dropped ("the interview I uploaded"), find it here by name and media.import {source: {upload_id}} it; complete says it is all in. Listing does not count as a use, so nothing here lasts longer for being listed.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`media`	Yes	Imported and created media, most recently used first (up to 200)
`storage`	Yes
`uploads`	Yes	Files sent to the server and not imported yet, newest first (up to 200): through media.upload, or dropped on the cuttingfloor site by the user
`media_count`	Yes	All media held, including any not listed
`upload_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 8, 2026

changedOutput schema / properties / media / items / properties / origin / properties / via / description

Previous value: -"upload: sent through a media.upload link, dropped on the account page, or a data: URI"New value: +"upload: sent through a media.upload link, dropped on the cuttingfloor site, or a data: URI"

changedOutput schema / properties / storage / properties / max_bytes / description

Previous value: -"The plan's cap; null for none"New value: +"This account's storage, in bytes; null for no limit"

changedOutput schema / properties / uploads / description

Previous value: -"Files sent to the server and not imported yet, newest first (up to 200): through media.upload, or dropped on the account page by the user"New value: +"Files sent to the server and not imported yet, newest first (up to 200): through media.upload, or dropped on the cuttingfloor site by the user"

Changed5 schema fields changedNov 1, 2026

addedOutput schema / properties / media / items / properties / origin / properties / frame
```
Added value: +{
+  "description": "still: the frame",
+  "type": "number"
+}
```

changedOutput schema / properties / media / items / properties / origin / properties / from / description

Previous value: -"upload: a file the user sent; url: downloaded; path: a media root; render: an export.video; created: a create.* tool"New value: +"upload: a file the user sent; url: downloaded; path: a media root; render: an export.video; created: a create.* tool; still: a frame of a video or an edit"

changedOutput schema / properties / media / items / properties / origin / properties / from / enum

Previous value: -[
-  "upload",
-  "url",
-  "path",
-  "render",
-  "created"
-]New value: +[
+  "upload",
+  "url",
+  "path",
+  "render",
+  "created",
+  "still"
+]

addedOutput schema / properties / media / items / properties / origin / properties / media_id

Added value: +{
+  "description": "still: the video the frame is from",
+  "pattern": "^m_[0-9a-z]{26}$",
+  "type": "string"
+}

changedOutput schema / properties / media / items / properties / origin / properties / timeline_id / description

Previous value: -"render: the timeline that was exported"New value: +"render: the timeline that was exported; still: the edit the frame is from"

First observedOct 25, 2026

TDQS

Score is being calculated.

All cuttingfloor 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.