Skip to main content
Glama
Sign In
vimeo-mcp

vimeo-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get the full details of one video

get_video
Read-onlyIdempotent

Retrieve full details for a Vimeo video—description, embed URL, thumbnail, privacy, tags, and transcode status—by numeric ID, /videos/ URI, or vimeo.com URL.

Instructions

Get the full details of one video: description, embed URL, thumbnail, privacy, tags and transcode status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "video_id": "<video_id>"
    },
    "name": "get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYesVideo id. A numeric id, a /videos/ URI or a vimeo.com URL all work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and repeatability profile is fully covered. The description adds the set of fields that come back, which is useful context, but says nothing about auth scope, error behavior for a missing id, 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.

Conciseness5/5

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

One front-loaded sentence with zero filler; the verb and resource lead and the field list follows compactly.

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?

With no output schema, the description compensates by enumerating the returned fields, which is the main thing an agent would otherwise lack. Remaining gaps are minor for a single-id read tool covered by annotations.

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 100% and the single video_id parameter is documented well in the schema (numeric id, /videos/ URI, or vimeo.com URL all accepted). The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 ("Get the full details of one video") and enumerates the payload (description, embed URL, thumbnail, privacy, tags, transcode status), which signals it is the comprehensive single-video read. It does not explicitly contrast itself with siblings like get_video_stats, get_video_privacy, or get_download_links, so an agent must infer the boundary from the word "full".

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 or when-not-to-use guidance and no named alternative. The description never says to prefer this over get_video_stats, get_video_privacy, or search_videos when a single record is already known by id.

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

Deploy Server

Other Tools