Vimeo

Video

video

Read-onlyIdempotent

Fetch metadata for a single Vimeo video by numeric or string ID; returns title, description, duration, embed URLs, privacy settings, stats, and owner info.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`uri`	No	Video URI
`name`	No	Video title
`tags`	No	Video tags
`user`	No	Uploader user object
`embed`	No	Embed settings
`stats`	No	Video statistics
`width`	No	Video width
`height`	No	Video height
`status`	No	Video processing status
`license`	No	License type
`privacy`	No	Privacy settings
`duration`	No	Duration in seconds
`metadata`	No	Additional metadata
`pictures`	No	Picture/thumbnail data
`description`	No	Video description
`created_time`	No	Creation timestamp
`release_time`	No	Release timestamp
`modified_time`	No	Last modified timestamp
`content_rating`	No	Content ratings

Schema Changelog

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

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": "76979871"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "content_rating": {
+      "description": "Content ratings",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "created_time": {
+      "description": "Creation timestamp",
+      "type": "string"
+    },
+    "description": {
+      "description": "Video description",
+      "type": "string"
+    },
+    "duration": {
+      "description": "Duration in seconds",
+      "type": "number"
+    },
+    "embed": {
+      "description": "Embed settings",
+      "type": "object"
+    },
+    "height": {
+      "description": "Video height",
+      "type": "number"
+    },
+    "license": {
+      "description": "License type",
+      "type": "string"
+    },
+    "metadata": {
+      "description": "Additional metadata",
+      "type": "object"
+    },
+    "modified_time": {
+      "description": "Last modified timestamp",
+      "type": "string"
+    },
+    "name": {
+      "description": "Video title",
+      "type": "string"
+    },
+    "pictures": {
+      "description": "Picture/thumbnail data",
+      "type": "object"
+    },
+    "privacy": {
+      "description": "Privacy settings",
+      "type": "object"
+    },
+    "release_time": {
+      "description": "Release timestamp",
+      "type": "string"
+    },
+    "stats": {
+      "description": "Video statistics",
+      "type": "object"
+    },
+    "status": {
+      "description": "Video processing status",
+      "type": "string"
+    },
+    "tags": {
+      "description": "Video tags",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "uri": {
+      "description": "Video URI",
+      "type": "string"
+    },
+    "user": {
+      "description": "Uploader user object",
+      "type": "object"
+    },
+    "width": {
+      "description": "Video width",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedMay 24, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "id": "76979871"
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "content_rating": {
-      "description": "Content ratings",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "created_time": {
-      "description": "Creation timestamp",
-      "type": "string"
-    },
-    "description": {
-      "description": "Video description",
-      "type": "string"
-    },
-    "duration": {
-      "description": "Duration in seconds",
-      "type": "number"
-    },
-    "embed": {
-      "description": "Embed settings",
-      "type": "object"
-    },
-    "height": {
-      "description": "Video height",
-      "type": "number"
-    },
-    "license": {
-      "description": "License type",
-      "type": "string"
-    },
-    "metadata": {
-      "description": "Additional metadata",
-      "type": "object"
-    },
-    "modified_time": {
-      "description": "Last modified timestamp",
-      "type": "string"
-    },
-    "name": {
-      "description": "Video title",
-      "type": "string"
-    },
-    "pictures": {
-      "description": "Picture/thumbnail data",
-      "type": "object"
-    },
-    "privacy": {
-      "description": "Privacy settings",
-      "type": "object"
-    },
-    "release_time": {
-      "description": "Release timestamp",
-      "type": "string"
-    },
-    "stats": {
-      "description": "Video statistics",
-      "type": "object"
-    },
-    "status": {
-      "description": "Video processing status",
-      "type": "string"
-    },
-    "tags": {
-      "description": "Video tags",
-      "items": {
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "uri": {
-      "description": "Video URI",
-      "type": "string"
-    },
-    "user": {
-      "description": "Uploader user object",
-      "type": "object"
-    },
-    "width": {
-      "description": "Video width",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": "76979871"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "content_rating": {
+      "description": "Content ratings",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "created_time": {
+      "description": "Creation timestamp",
+      "type": "string"
+    },
+    "description": {
+      "description": "Video description",
+      "type": "string"
+    },
+    "duration": {
+      "description": "Duration in seconds",
+      "type": "number"
+    },
+    "embed": {
+      "description": "Embed settings",
+      "type": "object"
+    },
+    "height": {
+      "description": "Video height",
+      "type": "number"
+    },
+    "license": {
+      "description": "License type",
+      "type": "string"
+    },
+    "metadata": {
+      "description": "Additional metadata",
+      "type": "object"
+    },
+    "modified_time": {
+      "description": "Last modified timestamp",
+      "type": "string"
+    },
+    "name": {
+      "description": "Video title",
+      "type": "string"
+    },
+    "pictures": {
+      "description": "Picture/thumbnail data",
+      "type": "object"
+    },
+    "privacy": {
+      "description": "Privacy settings",
+      "type": "object"
+    },
+    "release_time": {
+      "description": "Release timestamp",
+      "type": "string"
+    },
+    "stats": {
+      "description": "Video statistics",
+      "type": "object"
+    },
+    "status": {
+      "description": "Video processing status",
+      "type": "string"
+    },
+    "tags": {
+      "description": "Video tags",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "uri": {
+      "description": "Video URI",
+      "type": "string"
+    },
+    "user": {
+      "description": "Uploader user object",
+      "type": "object"
+    },
+    "width": {
+      "description": "Video width",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, destructiveHint. Description adds specifics on returned fields (title, duration, etc.), providing moderate additional context without contradicting annotations.

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?

Single sentence that front-loads purpose and efficiently conveys key information with no wasted words.

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

Completeness5/5

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

Given single parameter, rich annotations, and presence of output schema, the description sufficiently covers the tool's behavior and return values, leaving no critical gaps.

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 has 0% description coverage. Description mentions 'numeric or string ID' and provides an example, adding some meaning beyond schema, but does not fully explain constraints or format, so baseline is 3.

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?

Description clearly states 'Fetch metadata for a single Vimeo video by numeric or string ID', specifying verb, resource, and method. It differentiates from siblings that deal with lists or other entities by focusing on a single video retrieval and listing return fields.

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 implies usage for fetching a single video by ID, and siblings include search and list tools, but no explicit guidance on when not to use or alternatives is provided.

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

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.

Video

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources