Vimeo MCP Server and API by Cotlet

Search videos in Vimeo

vimeo_search_videos

Read-onlyIdempotent

Search videos in the user's own Vimeo account from ChatGPT, Claude or any AI agent. Returns how to do it in Vimeo step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Vimeo Cloud Browser. Vimeo's official API: Vimeo has a full REST API with OAuth 2.0 and an official remote MCP server in public beta that covers only part of it (checked 17 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vimeo_search_videos"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-open-world, and the description adds genuinely new behavior: it produces a screen-by-screen how-to (screens, buttons, fields) and performs no browser action itself. That is the key trait an agent needs. It does not describe the returned content's structure or size, which keeps it below a 5.

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

Conciseness3/5

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

The operational sentences are front-loaded and tight, but the closing note about Vimeo's REST API, OAuth 2.0, and a public-beta remote MCP server adds no invocation value and ends the description on a tangent. Removing it would sharpen the definition without losing anything an agent needs.

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 zero-parameter, read-only guidance tool with no output schema and annotation coverage, the description supplies what's needed: what it returns, that it has no side effects, and where to go next. It could say more about what happens if the user is not authenticated, but it is largely self-sufficient.

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

Parameters4/5

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

The tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level gaps exist.

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?

Names a specific verb and resource ('Search videos in the user's own Vimeo account') but immediately reframes it: the tool returns step-by-step instructions rather than search results. That distinction is stated explicitly, so an agent can tell it apart from a real search, though the name/title 'Search videos' still invites a misread that the description must correct.

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?

Gives a clear usage path: call this first, then perform the action with the cotlet_browser_* tools in the user's Vimeo Cloud Browser, and notes it 'opens nothing by itself'. It does not state when-not to use it or how it relates to the other vimeo_* siblings, but the follow-up routing is unambiguous.

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

All Vimeo MCP Server and API by Cotlet 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.

Resources

Need Help?