Skip to main content
Glama

Vimeo

by io.github.pipeworx-io

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sortNo
queryYes
filterNo
per_pageNo
directionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoArray of matching videos
pageNoCurrent page
totalNoTotal matching videos
pagingNoPagination links
per_pageNoItems per page

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds valuable context by disclosing the authentication requirement ('authenticated with a Vimeo access token') and summarizing the response contents (title, duration, URLs, owner, play statistics), which goes beyond what annotations provide.

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

Conciseness5/5

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

The description is compact and front-loaded, with the core action and resource in the first sentence. Each subsequent sentence adds distinct information (parameters/auth, return fields, use case), and there is no redundant or filler text.

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?

Given the 6-parameter schema, strong annotations, and an output schema, the description covers the essential aspects: purpose, auth, key parameter names, and returned data. It is slightly incomplete in explaining parameter value constraints, but overall it provides enough context for an agent to select and invoke the tool.

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 description coverage is 0%, so the description must compensate for the 6 parameters. It names the parameters (page, per_page, sort, direction, filter) and clarifies that query is free-text, but it does not explain allowed values, semantics of sort/filter/direction, or effects of pagination parameters. This is only minimal compensation.

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

Purpose5/5

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

The description clearly identifies the tool as a free-text search over the Vimeo video library via api.vimeo.com/videos, with a specific verb ('Search') and resource ('Vimeo video library'). It also distinguishes itself from sibling tools like video, user_videos, or category_videos by emphasizing a library-wide subject/title/creator search.

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

Usage Guidelines4/5

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

The description states the intended use case: 'Answers which videos hosted on Vimeo match a subject, title, or creator name.' This provides clear context for when to use the tool, though it does not explicitly mention alternative tools or exclusionary guidance, so it falls short of a 5.

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

All Vimeo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates, and the polymarket_* family has six tools with blurred boundaries. The Vimeo tools are distinct, but the massive unrelated Pipeworx set creates ambiguity about which tool is appropriate for a given task.

Naming Consistency2/5

Tool names mix conventions: Vimeo tools use bare nouns (video, channel, user), while Pipeworx tools use verb_noun (resolve_entity, validate_claim) or noun_verb (ai_visibility_check). Some names like ask_pipeworx and pipeworx_feedback do not follow a consistent verb-first pattern.

Tool Count2/5

40 tools is far too many for a Vimeo server; only 9 tools are Vimeo-related, and the remaining 31 are an unrelated Pipeworx data toolkit. This inflates the surface area and makes the set unwieldy.

Completeness2/5

The Vimeo surface covers read operations (search, get, list) but lacks any write operations like upload, update, or delete videos. It also misses common Vimeo features like comments, likes, or portfolio management, so common tasks would hit dead ends.

Resources