Vimeo

User

user

Read-onlyIdempotent

Fetch a Vimeo user's public profile by user_id or vanity URL name; returns display name, bio, location, follower/following counts, and upload quota.

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": {
      "user_id": "user123"
    },
    "name": "user"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes

Output Schema

Name	Required	Description
`bio`	No	User biography
`uri`	No	User URI
`link`	No	Profile link
`name`	No	User name
`account`	No	Account type
`location`	No	User location
`metadata`	No	Additional metadata
`pictures`	No	Profile picture data
`websites`	No	Associated websites
`created_time`	No	Account creation timestamp

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "user_id": "user123"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "account": {
+      "description": "Account type",
+      "type": "string"
+    },
+    "bio": {
+      "description": "User biography",
+      "type": "string"
+    },
+    "created_time": {
+      "description": "Account creation timestamp",
+      "type": "string"
+    },
+    "link": {
+      "description": "Profile link",
+      "type": "string"
+    },
+    "location": {
+      "description": "User location",
+      "type": "string"
+    },
+    "metadata": {
+      "description": "Additional metadata",
+      "type": "object"
+    },
+    "name": {
+      "description": "User name",
+      "type": "string"
+    },
+    "pictures": {
+      "description": "Profile picture data",
+      "type": "object"
+    },
+    "uri": {
+      "description": "User URI",
+      "type": "string"
+    },
+    "websites": {
+      "description": "Associated websites",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, etc. The description adds value by listing the returned fields (display name, bio, location, etc.), which complements the safety profile.

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 front-loads the action and result, with no extraneous words.

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 simple tool with one parameter and an output schema, the description covers purpose, input, and output fields; lacks error handling details but is adequate.

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 description clarifies that the single parameter can be a user_id or vanity URL, adding meaning beyond the empty schema description, compensating for 0% coverage.

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 states the verb 'Fetch', resource 'Vimeo user's public profile', and scope 'by user_id or vanity URL name', distinguishing it from sibling tools like user_videos.

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 description implies usage context (by user_id or vanity URL) but lacks explicit guidance on when to use this tool vs alternatives such as user_videos.

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.