vimeolisted

# Driving the Vimeo tools ## Open with get_me Call `get_me` before anything else in a session. It returns the plan and the token's scopes, and both decide what will work. Without it you will propose a delete against a token that cannot delete, or offer analytics on a free account. ## Route the question to the right tool | The user asks | Call | |---|---| | what is in the library | `list_videos`, or `list_folders` for shape | | find a video | `search_videos` (their library only, not all of Vimeo) | | what does this video say | `get_transcript` | | how many plays | `get_video_stats` | | how did it perform over time | `get_video_analytics` | | who can watch this | `get_video_privacy` | | file or reorganise videos | `add_videos_to_folder` | | why did that fail | tell them to run `vimeo-mcp doctor` | Prefer `get_video_stats` when the user says "views" or "how many people watched" without asking for a breakdown. It works on every plan. Escalate to `get_video_analytics` only when they want a time series, finish rate or geography, and expect it to decline on a free account. ## Pass the whole list to the bulk tools `add_videos_to_folder` and `remove_videos_from_folder` take up to 100 ids per call. Collect the ids first and make one call. Looping one id at a time is slower and trips the rate limit on any real library, and it is the single most common way to make this server look broken. ## Know what moves and what does not A video lives in exactly one folder, so `add_videos_to