Vimeo

Videos Search

videos_search

Read-onlyIdempotent

Search the Vimeo video library through the Vimeo API (api.vimeo.com/videos) with a free-text query, plus page, per_page, sort, direction, and filter parameters, authenticated with a Vimeo access token. Returns matching Vimeo videos with title, description, duration, link and embed URLs, owner, and play statistics. Answers which videos hosted on Vimeo match a subject, title, or creator name.

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": {
      "query": "javascript tutorial"
    },
    "name": "videos_search"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`sort`	No
`query`	Yes
`filter`	No
`per_page`	No
`direction`	No

Output Schema

Name	Required	Description
`data`	No	Array of matching videos
`page`	No	Current page
`total`	No	Total matching videos
`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: +[
+  {
+    "query": "javascript tutorial"
+  },
+  {
+    "page": 1,
+    "per_page": 10,
+    "query": "motion design"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Array of matching videos",
+      "items": {
+        "properties": {
+          "created_time": {
+            "description": "Creation timestamp",
+            "type": "string"
+          },
+          "description": {
+            "description": "Video description",
+            "type": "string"
+          },
+          "duration": {
+            "description": "Duration in seconds",
+            "type": "number"
+          },
+          "height": {
+            "description": "Video height",
+            "type": "number"
+          },
+          "name": {
+            "description": "Video title",
+            "type": "string"
+          },
+          "pictures": {
+            "description": "Picture/thumbnail data",
+            "type": "object"
+          },
+          "uri": {
+            "description": "Video URI",
+            "type": "string"
+          },
+          "user": {
+            "description": "Uploader user object",
+            "type": "object"
+          },
+          "width": {
+            "description": "Video width",
+            "type": "number"
+          }
+        },
+        "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 matching videos",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the underlying API endpoint and the fact that a Vimeo access token is required for authentication.

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?

Three sentences, front-loaded with the core verb+resource and endpoint, with no wasted preamble. Slight repetition of 'Vimeo' and return-field detail that the output schema already covers keeps it from a 5.

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

Completeness3/5

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

Auth and endpoint are covered and an output schema exists so return values needn't be spelled out. However, for a 6-parameter search tool the missing semantics for sort/direction/filter and pagination behavior leave real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 6 parameters, so the description must carry the burden, yet it only names page, per_page, sort, direction, and filter without explaining accepted values, sort fields, or filter syntax. Only 'query' as free-text is clarified, leaving most parameter semantics undocumented.

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 (search) and resource (Vimeo video library via api.vimeo.com/videos) and clarifies it takes a free-text query. It implicitly distinguishes itself from siblings like user_videos/channel_videos by being a general library search, but never explicitly names the alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The final sentence ('Answers which videos hosted on Vimeo match a subject, title, or creator name') implies the use case, but there is no explicit when-to-use vs when-to-use-something-else guidance and no sibling alternatives are named.

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.