Vimeo

Channel Videos

channel_videos

Read-onlyIdempotent

List videos in a Vimeo channel by channel ID or slug; supports pagination 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": {
      "channel_id_or_slug": "staffpicks"
    },
    "name": "channel_videos"
  }
}

Input Schema

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

Output Schema

Name	Required	Description
`data`	No	Array of channel videos
`page`	No	Current page
`total`	No	Total videos in channel
`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: +[
+  {
+    "channel_id_or_slug": "staffpicks"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Array of channel 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 in channel",
+      "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 by structured data. The description adds that pagination and sorting are supported and that the result is a metadata array, but says nothing about defaults, result caps, or rate limits.

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 dense sentence with the resource and key front-loaded and no filler. The semicolon-chained clauses make it slightly run-on, but every phrase carries information.

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?

For a read-only list endpoint with an output schema present, the description need not explain return values in detail and correctly points at a metadata array. It covers pagination and sorting at a high level; the remaining gap is the absence of defaults and sort/direction value semantics.

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% across 5 parameters, so the description must carry the load. It loosely groups the parameters into pagination (page, per_page) and sorting (sort, direction) and names the required key, but gives no valid values, direction tokens, or per_page bounds, leaving the enums-less schema under-explained.

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 and resource ('List videos in a Vimeo channel') plus the lookup key (channel ID or slug). This implicitly separates it from user_videos and category_videos, though it never names those siblings, so differentiation requires the agent to infer it from the resource noun.

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 explicit when-to-use guidance, no prerequisites, and no named alternatives such as category_videos, user_videos, or videos_search. Usage is only inferable from the resource being listed.

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.