flask

Browse contents. Without folder_id: lists what's at the team's top level (root) — both folders and assets that live directly at root. With folder_id: opens that folder and returns its child folders and assets. Each asset item carries asset_id (the asset), version_id (its current version), version_count, its media fields, url (always the newest version) and version_url.

{
  "type": "object",
  "properties": {
    "folder_id": {
      "description": "Folder to open — omit to see team root",
      "type": "string"
    },
    "limit": {
      "description": "Page size (default 20, max 100)",
      "type": "number"
    },
    "offset": {
      "description": "Items to skip for pagination",
      "type": "number"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

List top-level feedback on an asset (pass the asset id for its current version, or a version id for that exact version). Returns each item's text body, tags (by name), author, timestamp, and reply_count. Recording items are ONE comment per recording: the text body is the AI-organized feedback, and the recording object adds the full verbatim transcript plus visual_references (the pointing phrases with the recording time each was spoken). Items with visual attachments carry images (attached image files) and/or has_drawing: true (a drawing made on the asset) - call get_annotated_frames to see them. Use feedback_get to read full reply threads.

{
  "type": "object",
  "properties": {
    "asset_id": {
      "type": "string",
      "description": "Asset id (its current version) or version id to list feedback for"
    },
    "limit": {
      "description": "Page size (default 20, max 100)",
      "type": "number"
    },
    "offset": {
      "description": "Items to skip for pagination",
      "type": "number"
    }
  },
  "required": [
    "asset_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Get a single feedback item with its full reply thread. Returns the item's text body (for recordings: the AI-organized feedback), tags (by name), author, video timestamp, the recording's full verbatim transcript, visual_references (the pointing phrases - "this", "over here" - with the recording time each was spoken; feed them to get_frame to see what was being pointed at), visual attachments (images / has_drawing - render them with get_annotated_frames), and all nested replies.

{
  "type": "object",
  "properties": {
    "element_id": {
      "type": "string",
      "description": "Feedback item ID to retrieve"
    }
  },
  "required": [
    "element_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Wait for NEW feedback on an asset. Blocks up to timeout_seconds (default 45) and returns as soon as feedback newer than `since` arrives, or times out with an empty list. To listen continuously, call it again with the returned next_since. Use this after uploading a video for review instead of repeatedly calling feedback_list.

{
  "type": "object",
  "properties": {
    "asset_id": {
      "type": "string",
      "description": "Asset id (its current version) or version id to watch for new feedback"
    },
    "since": {
      "description": "ISO timestamp — only feedback created after this is returned. Omit on the first call (defaults to now, i.e. waits for the NEXT feedback). On subsequent calls pass the next_since from the previous response.",
      "type": "string"
    },
    "timeout_seconds": {
      "description": "How long to wait before returning empty (10-50, default 45)",
      "type": "number"
    }
  },
  "required": [
    "asset_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Create a feedback comment on an asset, as the connected user. Pass an asset id (the comment lands on its current version) or a version id (that exact version). PREFER passing timestamp (seconds into the video) whenever the source material has one - e.g. when importing feedback from an email like 'at 0:42 the logo is wrong', convert 0:42 to 42. Without timestamp the comment is a general (non-anchored) note. tags applies the team's EXISTING tags by name (see the tags tool); statuses are tags too. Use reply_to to reply in an existing thread. Cannot attach recordings, drawings, or images.

{
  "type": "object",
  "properties": {
    "asset_id": {
      "type": "string",
      "minLength": 1,
      "description": "Asset id (current version) or version id to comment on"
    },
    "content": {
      "type": "string",
      "minLength": 1,
      "maxLength": 10000,
      "description": "The comment text (plain text)"
    },
    "timestamp": {
      "description": "Video time in SECONDS the comment refers to (e.g. 72.5 for 1:12.5). Strongly preferred when known; omit for a general comment.",
      "type": "number"
    },
    "tags": {
      "description": "Tag NAMES to apply (must already exist in the team - see the tags tool)",
      "maxItems": 20,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      }
    },
    "reply_to": {
      "description": "Feedback item id to reply to (threads the comment under it)",
      "type": "string"
    }
  },
  "required": [
    "asset_id",
    "content"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Edit an existing feedback item. content (replaces the text) and timestamp (video time in seconds) can only be changed on the connected user's OWN comments. add_tags / remove_tags apply the team's existing tags by NAME and work on ANY feedback item you can comment on (labels and statuses are collaborative - e.g. add the 'Done' tag to mark feedback resolved). Provide at least one of content, timestamp, add_tags, remove_tags.

{
  "type": "object",
  "properties": {
    "element_id": {
      "type": "string",
      "minLength": 1,
      "description": "Feedback item to edit"
    },
    "content": {
      "description": "New comment text (fully replaces the existing text; own comments only)",
      "type": "string",
      "minLength": 1,
      "maxLength": 10000
    },
    "timestamp": {
      "description": "New video time in SECONDS the comment refers to (own comments only)",
      "type": "number"
    },
    "add_tags": {
      "description": "Tag NAMES to add (must already exist in the team)",
      "maxItems": 20,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      }
    },
    "remove_tags": {
      "description": "Tag NAMES to remove",
      "maxItems": 20,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      }
    }
  },
  "required": [
    "element_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Supplementary visuals for a feedback item. For recording items: the media under review with the reviewer's drawing rendered in, plus their shared SCREEN when they demonstrated something (e.g. a Photoshop/Figma mockup); webcam frames are NOT included, and the transcript is returned marked [FRAME N]. Also works for text comments that carry visuals: a standalone drawing (has_drawing: true) is rendered onto the frame it was drawn over, and attached images (images array) are returned as frames. If a visual reference is still unclear, call get_frame to drill into a specific moment (at) or spoken word/phrase (word). Returns up to 12 images.

{
  "type": "object",
  "properties": {
    "element_id": {
      "type": "string",
      "description": "The feedback item (element) to get annotated frames for"
    }
  },
  "required": [
    "element_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Drill into a recording for MORE visual detail: get the exact frame at a specific time (at) or when a specific word/phrase was spoken (word). Use when get_annotated_frames did not show what a reference ('this','here','that') means, or to see a moment the transcript mentions. Returns the asset frame at that moment (plus the active shared screen, if any) and a transcript snippet around it.

{
  "type": "object",
  "properties": {
    "element_id": {
      "type": "string",
      "description": "The recording feedback item (element) to drill into"
    },
    "at": {
      "description": "recording time in seconds",
      "type": "number"
    },
    "word": {
      "description": "a word or short phrase the reviewer spoke",
      "type": "string"
    },
    "source": {
      "description": "limit to the asset frame or the shared-screen frame",
      "type": "string",
      "enum": [
        "asset",
        "screen"
      ]
    }
  },
  "required": [
    "element_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Check the processing status of a video. Pass the version id an upload returned (asset_id), or an asset id (resolves to its current version). Returns progress percentage for videos being processed, confirms it is ready, or reports no_versions for an asset that has no media yet.

{
  "type": "object",
  "properties": {
    "asset_id": {
      "type": "string",
      "description": "Version id (from an upload) or asset id to check"
    }
  },
  "required": [
    "asset_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

See who has access to a folder or an asset and their permission levels (full_access, comment, view, none). Returns the connected user's effective access, the creator, plus link and team-member default access levels. Pass folder_id for a folder, or asset_id for an asset (an asset id or any of its version ids - permissions live on the asset, versions inherit them).

{
  "type": "object",
  "properties": {
    "folder_id": {
      "description": "Folder to check permissions for (or pass asset_id)",
      "type": "string"
    },
    "asset_id": {
      "description": "Asset (or version) to check permissions for",
      "type": "string"
    },
    "limit": {
      "description": "Page size for members (default 20, max 100)",
      "type": "number"
    },
    "offset": {
      "description": "Members to skip for pagination",
      "type": "number"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Search across your team's folders, assets, and feedback by text. Always returns all three categories together.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Text to search for"
    },
    "limit": {
      "description": "Max results per category (default 10, max 50)",
      "type": "number"
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Get the latest comments across your team, newest first. Returns a mix of text and recording comments with author, timestamp, and a link to jump into the conversation. Each item has a `type` field ("text" or "recording") plus the asset it belongs to (container_id / container_title), the version it was left on (asset_id = version id, version number), so you can read feedback across many videos in one call. Scope with folder_id to read one client's/project's feedback, narrow the window with since/until, and page with offset. For counts and trends use feedback_stats instead.

{
  "type": "object",
  "properties": {
    "limit": {
      "description": "Number of comments to return (default 20, max 100)",
      "type": "number"
    },
    "offset": {
      "description": "Items to skip for pagination (use next_offset from the previous response)",
      "type": "number"
    },
    "folder_id": {
      "description": "Only feedback on assets inside this folder's subtree",
      "type": "string"
    },
    "since": {
      "description": "Only feedback created at/after this ISO timestamp",
      "type": "string"
    },
    "until": {
      "description": "Only feedback created at/before this ISO timestamp",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

List the team's tags and show the share of each tag (plus an 'untagged' bucket) across a scope. Scope defaults to the whole team; pass folder_id to narrow to one folder (its whole subtree), or asset_id to narrow to one asset (an asset id counts feedback across ALL its versions; a version id widens to its asset). Shares are count_with_tag / total_elements and do NOT sum to 100% because elements can carry multiple tags.

{
  "type": "object",
  "properties": {
    "folder_id": {
      "description": "Narrow to this folder (mutually exclusive with asset_id)",
      "type": "string"
    },
    "asset_id": {
      "description": "Narrow to this asset (mutually exclusive with folder_id)",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Upload a video from a public URL (a direct video file link or a Google Drive share link) into Flask. Flask downloads it, stores it, and starts processing. Creates a new asset (container_id + url) with the file as its first version (asset_id / version_id), or a new version of an existing asset with version_of. Share the returned asset URL while processing; poll asset_status(version_id) until status is "ready" before reporting processing complete. folder_id is OPTIONAL: omit it to upload to the team's top level (root). Free to use for up to 100 MCP uploads; beyond that the user needs a plan at https://flask.do/plan. You still need edit access on the folder if one is given. For a LOCAL file on disk, use upload_file_start instead.

{
  "type": "object",
  "properties": {
    "video_url": {
      "type": "string",
      "description": "Public URL of the video to import - a direct video file URL or a Google Drive share link"
    },
    "folder_id": {
      "description": "Optional folder to upload into (you must have edit access - check with permission_get if unsure). Omit to upload to the team's top level (root).",
      "type": "string"
    },
    "title": {
      "description": "Title for the new asset (defaults to \"Video from URL\")",
      "type": "string"
    },
    "version_of": {
      "description": "Upload as a NEW VERSION of an existing asset instead of creating a separate asset. Accepts the id of the asset (its container id, what contents/search return), or of any of its versions. The new upload becomes the current version; the asset's url then shows it. folder_id is ignored when version_of is given.",
      "type": "string"
    }
  },
  "required": [
    "video_url"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Start uploading a LOCAL video file from the user's machine into Flask. Creates the asset immediately (container_id + shareable url, live before any bytes move) with the file as its version (asset_id / version_id), or a new version of an existing asset with version_of, and returns a presigned upload URL. After calling this, upload the file bytes with the curl command from next_step, then call upload_file_complete. folder_id is OPTIONAL: omit it to upload to the team's top level (root). Max file size 5GB. Free to use for up to 100 MCP uploads; beyond that the user needs a plan at https://flask.do/plan. You still need edit access on the folder if one is given.

{
  "type": "object",
  "properties": {
    "folder_id": {
      "description": "Optional folder to upload into (you must have edit access - check with permission_get if unsure). Omit to upload to the team's top level (root).",
      "type": "string"
    },
    "file_size": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991,
      "description": "Exact size of the local file in bytes (e.g. from `stat -f%z <file>` on macOS or `stat -c%s <file>` on Linux)"
    },
    "title": {
      "description": "Title for the new asset (defaults to \"Untitled Video\")",
      "type": "string"
    },
    "content_type": {
      "description": "MIME type of the file (defaults to video/mp4)",
      "type": "string"
    },
    "version_of": {
      "description": "Upload as a NEW VERSION of an existing asset instead of creating a separate asset. Accepts the id of the asset (its container id, what contents/search return), or of any of its versions. The new upload becomes the current version; the asset's url then shows it. folder_id is ignored when version_of is given.",
      "type": "string"
    }
  },
  "required": [
    "file_size"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Finalize a local file upload started with upload_file_start. Call this only AFTER the curl PUT has finished successfully. Verifies the file landed in storage and starts video processing. Safe to retry.

{
  "type": "object",
  "properties": {
    "asset_id": {
      "type": "string",
      "description": "The asset_id (version id) returned by upload_file_start"
    },
    "version_of": {
      "description": "Ignored (kept for older clients): the version is attached at upload_file_start.",
      "type": "string"
    }
  },
  "required": [
    "asset_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Aggregate feedback statistics across many assets in ONE call - counts per asset and per version (v1, v2, ...), split by type (text/recording), tag, and author, with first/last feedback timestamps. Scope to a folder (folder_id), one asset (asset_id - an asset id or any of its version ids; the whole asset is reported, version by version), or the whole team; narrow the time window with from/to. Each item carries container_id (the asset) and its versions. Use this for trend questions like 'are v1 notes going down across this client's recent videos' or 'what tags dominate this folder' instead of calling feedback_list per asset. For reading the feedback text itself across assets, use recent_activity.

{
  "type": "object",
  "properties": {
    "folder_id": {
      "description": "Scope to this folder's subtree (mutually exclusive with asset_id)",
      "type": "string"
    },
    "asset_id": {
      "description": "Scope to one asset or version stack (mutually exclusive with folder_id)",
      "type": "string"
    },
    "from": {
      "description": "Only count feedback created at/after this ISO timestamp",
      "type": "string"
    },
    "to": {
      "description": "Only count feedback created at/before this ISO timestamp",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}