Vimeo

User Videos

user_videos

Read-onlyIdempotent

List videos uploaded by a Vimeo user (user_id); supports pagination (page, per_page) and sorting; returns video metadata array.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

Name	Required	Description	Default
`page`	No
`sort`	No
`user_id`	Yes
`per_page`	No
`direction`	No

Output Schema

Name	Required	Description
`data`	No	Array of user videos
`page`	No	Current page
`total`	No	Total videos by user
`paging`	No	Pagination links
`per_page`	No	Items per page

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026
- changedOutput schema / properties / data / items / properties / description / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "user_id": "user123"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Array of user videos",
+      "items": {
+        "properties": {
+          "created_time": {
+            "description": "Creation timestamp",
+            "type": "string"
+          },
+          "description": {
+            "description": "Video description",
+            "type": "string"
+          },
+          "duration": {
+            "description": "Duration in seconds",
+            "type": "number"
+          },
+          "name": {
+            "description": "Video title",
+            "type": "string"
+          },
+          "pictures": {
+            "description": "Picture/thumbnail data",
+            "type": "object"
+          },
+          "uri": {
+            "description": "Video URI",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "page": {
+      "description": "Current page",
+      "type": "number"
+    },
+    "paging": {
+      "description": "Pagination links",
+      "type": "object"
+    },
+    "per_page": {
+      "description": "Items per page",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total videos by user",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds that pagination and sorting are supported and that a metadata array is returned, which is modest additional context but no details on paging limits or error behavior.

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

Conciseness4/5

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

A single front-loaded sentence using semicolons to separate purpose, parameters, and return shape. Every clause carries information; the only minor cost is that the pagination/sorting clause is compressed into one phrase.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be detailed, and annotations cover the safety profile for this simple read-only listing tool. The remaining gaps are pagination defaults and sort-field vocabulary, which are minor for a list endpoint.

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 0%, so the description carries the burden and does name user_id plus the pagination/sorting parameters. But it gives no value semantics: no accepted sort field names, no default per_page, no meaning for direction, and 'sorting' only loosely maps to the sort/direction pair.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (list) and resource (videos) scoped to a Vimeo user via user_id, which separates it from generic siblings like video and videos_search. It does not, however, explicitly name an alternative tool the way the best-in-class examples do, so the distinction with videos_search/category_videos is only implicit.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. With siblings such as videos_search, channel_videos, and user in the set, the description should say why an agent picks this over those, and it does not.

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

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